/usr/src/sys/i386/isa/if_ar.c
/usr/src/sys/i386/isa/if_sr.c
John
>
> Any source we can have a look at (probe/attach/*_MODULE)?
>
> Nick
>
> On Wed, 28 Jul 1999, John Hay wrote:
>
> > Nope, it is an ISA driver and I wasn't that brave. :-) It is part of
> > standard FreeBSD and I just compiled it into the kernel with a kernel
> > config file.
> >
> > > Are you by any chance kldload'ing the module for testing?
> > >
> > > If so you should have:
> > >
> > > DEVMETHOD(bus_driver_added, bus_generic_driver_added),
> > >
> > > For your 'arc' device_method_t method declaration.
> > >
> > > I got bit by this one too.
> > >
> > > On Wed, 28 Jul 1999, John Hay wrote:
> > > > I have been trying to get my ar(4) and sr(4) drivers going again on -current,
> > > > but it seems that the newbus code doesn't like my little trick that worked
> > > > for so long. :-(
> > > >
> > > > Basically the drivers are called ar0 in the kernel config file, but in
> > > > the isa_driver struct I call them arc and not ar, because the chip that
> > > > is used actually have 2 ports and I register them seperately as ar0 and
> > > > ar1 during the attach phase.
> > > >
> > > > >From what I can see now, it looks like the newbus code doesn't even
> > > > call the arprobe routine. I have even added a printf right in the start
> > > > of it, but it never prints anything. Just as a test I changed my kernel
> > > > config file and files.i386 from ar to arc and then it works.
> > > >
> > > > So what should I do? Can the newbus code be fixed to work in this case
> > > > too or should I newbusify the drivers and will that help? Won't that
> > > > create a clash because of the isa compatabilty shim?
> > > >
> >
> > John
> > --
> > John Hay -- [EMAIL PROTECTED]
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> >
> >
>
> --
> ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy
>
--
John Hay -- [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
