Rink Springer wrote:
>
> - Original Message -
> From: "Mike Smith" <[EMAIL PROTECTED]>
>
> > Sounds like you're overflowing the printer's buffer. When you say "it
> > worked fine" under RedHat, did you actually attempt to print a large job?
> Yup, I did, and it worked nicely.
> >
> > T
Terry Lambert wrote:
>
> > Back in July I was asking about the capability to set parameters (variables)
> > when loading my DSL driver module. There was a small flurry of activity
> > about some initial ideas on how to do it, but I never heard any more about
> > it. Did you (Mike, Warner, or a
Terry,
First, thanks for the reply.
> > Back in July I was asking about the capability to set parameters (variables)
> > when loading my DSL driver module. There was a small flurry of activity
> > about some initial ideas on how to do it, but I never heard any more about
> > it. Did you (Mike
Back in July I was asking about the capability to set parameters (variables)
when loading my DSL driver module. There was a small flurry of activity
about some initial ideas on how to do it, but I never heard any more about
it. Did you (Mike, Warner, or anybody) have time to work on it? Did th
[ I'm sending this to the list just in case anyone searches the
email archives for an answer to a similar question. ]
I wrote:
> > Now since the MBR booter "knows" that you don't boot DOS/Windows
> > from an "extended" partition (type 5), it doesn't offer it as
> > a boot choice. Now I coul
I have a notebook PC with Windows, Linux, and FreeBSD on it.
I installed the FreeBSD booter into the Master Boot Record (MBR).
Using that, I can boot Windows or FreeBSD. But Linux doesn't
show up as a boot choice, because I installed it into a "dos
extended" partition (slice), to keep linux from
Peter Dufault wrote:
> you can have a Linda-like pool of work requests to hand out to a swarm of worker
>bees.
^^^
Could you please decode this for me? :)
Thanks,
Gary
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the bod
Devin Butterfield wrote:
>
> Hi all,
>
> In the process of learning device driver writing, I have written a
> simple skeleton driver for an isa PnP card I have.
>
> Although this driver works (successfully probes, attaches, and gets it's
> needed io resources) when compiled into the kernel, if
Warner Losh wrote:
>
> Something like the following?
>
> Comments?
>
> struct driver_param
> {
> const char *name;
> int (*fnp)(const char *, void *, void *);
> size_t off;
> void *argp;
> };
>
Perhaps instead of the "size_t off" above, which from the
code bel
Warner Losh wrote:
>
> Yes. You'd say
>
> hint.dslmodem.-1.TransmissionMode=LLC
What's the "-1" in the above?
> But writing this, I thin that normal enums would want a specialized
> routine for doing this that would could pass a table to.
Yes, a table of strings and enums seems like a gener
Mike Smith wrote:
>
> If you say "kldload foo", you load the file foo.ko. However, that file
> may contain more than one module.
I didn't know that was possible (i.e. supported)...
> The hints mechanism is what we are currently using to pass in the
> information that used to be in the kernel c
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Mike Smith writes:
> : > In message <[EMAIL PROTECTED]> "Gary T. Corcoran" writes:
> : > : No, I know it's not that easy. We need to be able to do things
> : > : like have "Transmiss
Archie Cobbs wrote:
>
> Warner Losh writes:
> > In message <[EMAIL PROTECTED]> "Gary T. Corcoran" writes:
> > : I was wondering if you (or anyone on this list) has had time
> > : to add module parameters to kldload? (and before anyone suggests
> >
Mike,
A couple of months ago we spoke about my needing the ability
to set module parameters during a kldload, and you indicated
that you would be working on them for FreeBSD 4.1.
I've since progressed my DSL driver to the point where it works
in all the modes I need (same as the Linux driver), b
"Jordan K. Hubbard" wrote:
>
> I'm sitting here in Seoul, Korea (which is very nice, by the way) and
> I've just managed to delete all 82 images of Kyoto off the FAT-12 format
> Smartcard they were on. Wh!
>
Way back in the Dark Ages I used to hack on FAT-12 code...
Going *way* back in th
Sergey Babkin wrote:
>
> Steven Alexander wrote:
> >
> > I've had problems getting Windows NT to boot using bootloaders from other
> > OSes. I'd suggest installing NT last and putting it on the first partition.
>
> The partition number does not really matter, what really matters is
> that Wind
Steve Hill wrote:
>
> Well, I am getting ready to attempt a quad-boot system. I wish to boot
> one of the following configurations:
>
>First CONFIG:
> - WinNT
> - FreeBSD
> - Linux
> - NetBSD
>
>Second CONFIG:
> - WinNT
> - FreeBSD
> - Linux
> -
Parthasarathy M. Aji wrote:
>
> Hey All,
> I know how to read and write to a text file in the user level , but I am
> assigned the task of reading data from a file while writing a kernel
> level C program. I don't know what functions to use, can any of you help
> me. If you can point me to some
Mike Smith wrote:
> > So, I want to know how I can "automagically" set the device options,
> > every time a user kldload's the device driver.
>
> If you want to support this mode of operation, you really don't have a
> lot of options right now.
> Well, teaching kldload about module parameters wo
Warner,
> Two options.
>
> Once is that you can get hints, the other is that you can get
> environment variables. The third is to have sysctls, but those can't
> be set until after the driver has finished loading. Which one do you
> want me to talk about?
I'm sorry, but I don't know what "hin
Now that my device driver basically works (I can successfully do pings
and ftp transfers through it) using default settings, I'd like to
start polishing it up a bit...
This is a driver for a DSL device (Lucent WildWire), and our driver
has lots of options because there are many "flavors" of DSL a
Warner Losh wrote:
> Original Message
> Subject: PCI DMA Questions
>
> I'm debugging a hunk of PCI hardware that I have under NDA. It
> doesn't seem to be initiating DMA transfers. This may be a hardware
> problem, but before I go back to the vendor, I want to make sure that
>
As I mentioned the other day, after installing FreeBSD 4.0-Release
I started getting random spontaneous reboots while in X (after running
FreeBSD 3.4-Release for 2 months without any problems). Now that I've
started debugging my driver, I enabled DDB, and now instead of
rebooting I'm crashing int
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> "Gary T. Corcoran" writes:
> : #define NdisRawReadPortUchar( _port, _ptr) *(_ptr) = inb((_port))
>
> Yes. The bus_space_handle_t that rman_get_bushandle returns on the
> i386 is the portnumber in I/O space
Mike Smith wrote:
> You're probably looking at code that thinks it can do "inb" and so forth;
Yep, more or less. That is, sprinkled throughout the code, there are things
of the form (just to give 1 example):
NdisRawReadPortUchar( (OneOfTheBaseAddresses + SomeOffset), &variable);
> sorry, we d
Warner,
> rid = 0x10;
> res1 = bus_alloc_resource(dev, SYS_RES_MEMORY, &rid, 0, ~0, 1, RF_ACTIVE);
...
> should do the trick. Change SYS_RES_MEMORY to SYS_RES_IOPORT if it is
> I/O mapped rather than memory mapped.
>
> In case it wasn't clear, the rid is the offset into the config space
> where
I installed FreeBSD 4.0 and I'm trying to write the attach() routine
for my device driver, to be compiled as a loadable module. In 4.0
the attach routine only gets passed a dev pointer, not a PCI configuration
pointer. My PCI device has up to 6 I/O ranges, and I need to get the
base addresses f
Mike Smith wrote:
> Go back to the module if this is for 4.x;
I originally asked about making a network driver module for 3.4.
I was hoping for either a "here's how you do it" or at least an "it's
not possible with 3.4" response...
> > Now this is a common codebase for this driver, which compi
Since I received exactly ZERO responses to my plea for help in making
my network device driver a loadable module, I'm now trying to compile
my driver into the kernel.
First, I made up a makefile and got my driver compiling cleanly
standalone in my directory. So the code is known good with resp
I'd like to know how to make the network device driver I'm
working on a loadable module. It's for a PCI device. I was
unable to find any examples of PCI network modules under /sys/pci.
The examples under /usr/share/examples/kld are not very helpful
either for a PCI network device.
It appears I
Darrell,
> > I'm trying to initialize a network device, and I'm trying to download
> > code *into* my device from some binary system files. There is no "user
> > space" or user process, for that matter, to deal with at this point. I
> > just want to (at this step) open a file(s) directly from m
"Matthew N. Dodd" wrote:
>
> On Fri, 17 Mar 2000, Gary T. Corcoran wrote:
> > I'm trying to initialize a network device, and I'm trying to download
> > code *into* my device from some binary system files. There is no
> > "user space"
Alfred,
> > Can someone please tell me how I can read a file from a device driver
> > in FreeBSD? I need to download 2 or 3 relatively-large code files to
> > my device, choosing from amongst several different files depending on
> > which mode I'm operating in. Therefore compiling-in the code
Can someone please tell me how I can read a file from a device driver
in FreeBSD? I need to download 2 or 3 relatively-large code files to
my device, choosing from amongst several different files depending on
which mode I'm operating in. Therefore compiling-in the code is not
a reasonable choic
34 matches
Mail list logo
