Re: Common device driver classes?
From: Julian Elischer (julian_at_elischer.org)
Date: 12/12/03
- Previous message: Nate Lawson: "Re: Common device driver classes?"
- In reply to: Nate Lawson: "Re: Common device driver classes?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 11 Dec 2003 17:32:21 -0800 (PST) To: Nate Lawson <nate@root.org>
On Thu, 11 Dec 2003, Nate Lawson wrote:
>
> Those would definitely be properties of the CPU and could be exported via
> sysctl. My need is a little different in that I need to attach a child
> driver to a cpu.
If I understand what was said.. then I agree that a buss for each CPU's
private "drivers", (one bus per cpu) off the root nexus
would make sense. One would assume also that PCPU(mybus)
would point to the bus, and that each bus would be able to identify it's
CPU. The question is how one schedules that control goes to the correct
cpu whe you try run that driver as it is likely if it is reading PCPU
registers etc. that it can only successfully run on that CPU.
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Nate Lawson: "Re: Common device driver classes?"
- In reply to: Nate Lawson: "Re: Common device driver classes?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
