Date: Wed, 28 Jul 1999 15:41:29 -0400 (EDT) From: "Matthew N. Dodd" <winter@jurai.net> To: John Hay <jhay@mikom.csir.co.za> Cc: current@FreeBSD.ORG Subject: Re: a little newbus problem Message-ID: <Pine.BSF.4.10.9907281538550.14648-100000@sasami.jurai.net> In-Reply-To: <199907281732.TAA48306@zibbi.mikom.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
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
>
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9907281538550.14648-100000>