> > > to avoid the hard-coded major numbers in the cdevsw[] entry that's
> > > passed? It seems like make_dev() should be able to roam cdevsw, find
> >
> > This is what devfs is meant to achieve. Unfortunately at the moment the
> > major numbers need to be fixed because there's no dynamism in
> > What does your driver do?
>
> It's not a driver as much as driver infrastructure. To measure the
> difficulty of porting the UDI Reference Implementation (available source
> soon!) I decided to try porting it to an OS that I knew little about.
Aha! I've been waiting for this since February
Robert Lipe wrote:
>
> Kenneth D. Merry wrote:
> > I do know that we have the concept of probe priorities, so you could
> > probably set up UDI to probe at a higher priority than the default system
> > drivers, and therefore attach instead of the default FreeBSD driver for a
> > given piece of h
Kenneth D. Merry wrote:
> On Mon, Nov 13, 2000 at 08:51:37 -0600, Robert Lipe wrote:
> > Kenneth D. Merry wrote:
>
> That is probably the direction you want to go in. We've got a device
> infrastructure already (new-bus), which is probably what you want to use.
This is the second mention I've h
On Mon, Nov 13, 2000 at 08:51:37 -0600, Robert Lipe wrote:
> Kenneth D. Merry wrote:
> > What does your driver do?
>
> It's not a driver as much as driver infrastructure. To measure the
> difficulty of porting the UDI Reference Implementation (available source
> soon!) I decided to try porting i
In message <[EMAIL PROTECTED]> Robert Lipe writes:
: Is there a "normal" way for a conforming driver to walk the busses,
: pluck out bus number, slot number, device id, subsystem id, and all that
: traditional stuff, or do I just need to carve up pci.c and build my own
: interface to do it?
You m
> > I have a need to walk the PCI bus, gleaning PCI IDs and other data.
> > (Yes, I know a dozen reasons why to NOT do that.) What I *almost*
> > need is the loop in pci_ioctl that walks pci_dev[]. The catch here is
>
> you doing things this way?
[ Answered in separate message. ]
> Are the
Kenneth D. Merry wrote:
> On Mon, Nov 13, 2000 at 00:44:10 -0600, Robert Lipe wrote:
> > I have a need to walk the PCI bus, gleaning PCI IDs and other data.
> > (Yes, I know a dozen reasons why to NOT do that.) What I *almost*
> > need is the loop in pci_ioctl that walks pci_dev[]. The catch he
> I'm new to FreeBSD, but an experienced kernel guy. I'm workgin with
> 4.1.1 on IA32 and need help understanding the ways of your world. :-)
> I'd like my project to look like a "normal" driver and use supported
> interfaces, but I'll patch the core code if I need to.
This willingness is good.
On Mon, Nov 13, 2000 at 00:44:10 -0600, Robert Lipe wrote:
> I'm new to FreeBSD, but an experienced kernel guy. I'm workgin with
> 4.1.1 on IA32 and need help understanding the ways of your world. :-)
> I'd like my project to look like a "normal" driver and use supported
> interfaces, but I'll pa
I'm new to FreeBSD, but an experienced kernel guy. I'm workgin with
4.1.1 on IA32 and need help understanding the ways of your world. :-)
I'd like my project to look like a "normal" driver and use supported
interfaces, but I'll patch the core code if I need to.
I have a need to walk the PCI bus,
11 matches
Mail list logo
