Subject: Re: console device selection
To: Jared D. McNeill <email@example.com>
From: Garrett D'Amore <firstname.lastname@example.org>
Date: 09/02/2006 09:31:21
Jared D. McNeill wrote:
> On 2-Sep-06, at 3:32 AM, Garrett D'Amore wrote:
>> Given this, how do folks feel about having wscons have this framework
>> for selecting console devices? It would mean tweaking a bunch of
>> console devices. But it would solve/cleanup the problem. As we are
>> getting more and more devices that can be console devices, it seems like
>> we need a unified way to select amongst them, especially as many of
>> these devices are potentially on expansion busses.
> Yes, please. This has been a pet peeve of mine for a long time.
> One comment about struct cons_device:
> int (*initialize)(void);
> This will need to take parameters. MD code may need to pass bus
> tags/handles to an MI driver (as is the case for vga), or in a more
> extreme case (igsfb_pci) it also needs a pci_chipset_tag_t, and the
> PCI bus/device/function numbers of the device. Not sure what other
> devices might need..
Hmm... that's interesting. I need to think about how to abstract this
out properly. I had been sort of assuming this would happen later in
the code (after devices attached) but clearly that isn't the case, you
need a console before attach is called.
I'm sure I can figure it out. :-)
Are you volunteering to help convert code? There are a lot of console
devices and ports out there.
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
Phone: 951 325-2134 Fax: 951 325-2191