Date: Mon, 12 Apr 1999 19:04:05 -0500 (EST) From: Alfred Perlstein <bright@rush.net> To: Doug Rabson <dfr@nlsystems.com> Cc: Peter Wemm <peter@netplex.com.au>, current@freebsd.org Subject: Re: cvs commit: sys/pci pci.c Message-ID: <Pine.BSF.3.96.990412185541.4169Y-100000@cygnus.rush.net> In-Reply-To: <Pine.BSF.4.05.9904122039220.74823-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 12 Apr 1999, Doug Rabson wrote: > On Mon, 12 Apr 1999, Alfred Perlstein wrote: > > > The problem that i faced was that the console stuff must be done even > > before the SYSINITs are done it's generally setup from machdep.c this > > is before a lot of stuff is really setup. > > > > How early can i expect this framework to be in place so i can attach > > a console bus/device or does it seem i have to hack this somehow? > > > > What i'm planning on is a way to modularize the console code enough > > so that during runtime the console can be moved from device to device > > and even support a forked console (i/o on both sio and sc) revoking > > a console and a split console (input serial, output syscons). > > That sounds very worthwhile. While you are at it, can you try to factor > out the common code from the i386 and alpha ports so that both can use the > new mechanism. I will try to, something i also wonder, why is there seperate sio.c for each port? it seems like a lot of the isa stuff is duplicated across each port making it hard to actually do this correctly. hopefull the new stuff going into the bus code will help this, i know drowning the code in #ifdef __alpha__/__i386__/etc is pretty nasty but trying to keep 3 sio.c and i presume more if the other arch ports in the works have the same isa device as even more difficult. the seperate i386/cons.c and such will be put into an arch independant form and i will impelement a spec to follow to be a console device. I will bring sio and syscons on i386 into this model and i hope developers with pc98 and alpha equip can move to it as well. > > btw, i'm not familiar with the proper way to use this list, am i generating > > noise by cc'ing the list or is that the proper way, or should move > > messages like this to -current? > > This is possibly material for the current list (although personally I > don't mind reading it here). moved to -current :) -Alfred 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.3.96.990412185541.4169Y-100000>