Re: Early printk behaviour

2007-08-20 Thread Gerd Hoffmann
Robin Getz wrote: >> Hmm, yes, should be doable in generic code. Check whenever the current >> console has CON_BOOT set and if so unregister it. > > Something like: > > +++ kernel/printk.c (working copy) > +int __init disable_boot_consoles(void) > +{ > + struct console *con; > + > +

Re: Early printk behaviour

2007-08-20 Thread Gerd Hoffmann
Robin Getz wrote: Hmm, yes, should be doable in generic code. Check whenever the current console has CON_BOOT set and if so unregister it. Something like: +++ kernel/printk.c (working copy) +int __init disable_boot_consoles(void) +{ + struct console *con; + + for

Re: Early printk behaviour

2007-08-17 Thread Robin Getz
On Fri 17 Aug 2007 17:09, Mike Frysinger pondered: > On 8/17/07, Robin Getz <[EMAIL PROTECTED]> wrote: > > > > Something like: > > > > Index: kernel/printk.c > > === > > --- kernel/printk.c (revision 3568) > > +++ kernel/printk.c

Re: Early printk behaviour

2007-08-17 Thread Mike Frysinger
On 8/17/07, Robin Getz <[EMAIL PROTECTED]> wrote: > On Fri 17 Aug 2007 03:49, Gerd Hoffmann pondered: > > Mike Frysinger wrote: > > >> Hmm, sort of, although I didn't think about the case of no real console > > >> replacing the early console. The intention of the patch is to have a > > >> smooth

Re: Early printk behaviour

2007-08-17 Thread Robin Getz
On Fri 17 Aug 2007 03:49, Gerd Hoffmann pondered: > Mike Frysinger wrote: > >> Hmm, sort of, although I didn't think about the case of no real console > >> replacing the early console. The intention of the patch is to have a > >> smooth handover from the boot console to the real console. And,

Re: Early printk behaviour

2007-08-17 Thread Gerd Hoffmann
Mike Frysinger wrote: >> Hmm, sort of, although I didn't think about the case of no real console >> replacing the early console. The intention of the patch is to have a >> smooth handover from the boot console to the real console. And, yes, if >> no real console is ever registered the boot

Re: Early printk behaviour

2007-08-17 Thread Gerd Hoffmann
Mike Frysinger wrote: Hmm, sort of, although I didn't think about the case of no real console replacing the early console. The intention of the patch is to have a smooth handover from the boot console to the real console. And, yes, if no real console is ever registered the boot console keeps

Re: Early printk behaviour

2007-08-17 Thread Robin Getz
On Fri 17 Aug 2007 03:49, Gerd Hoffmann pondered: Mike Frysinger wrote: Hmm, sort of, although I didn't think about the case of no real console replacing the early console. The intention of the patch is to have a smooth handover from the boot console to the real console. And, yes, if no

Re: Early printk behaviour

2007-08-17 Thread Mike Frysinger
On 8/17/07, Robin Getz [EMAIL PROTECTED] wrote: On Fri 17 Aug 2007 03:49, Gerd Hoffmann pondered: Mike Frysinger wrote: Hmm, sort of, although I didn't think about the case of no real console replacing the early console. The intention of the patch is to have a smooth handover from the

Re: Early printk behaviour

2007-08-17 Thread Robin Getz
On Fri 17 Aug 2007 17:09, Mike Frysinger pondered: On 8/17/07, Robin Getz [EMAIL PROTECTED] wrote: Something like: Index: kernel/printk.c === --- kernel/printk.c (revision 3568) +++ kernel/printk.c (working

Re: Early printk behaviour

2007-08-16 Thread Robin Getz
On Thu 16 Aug 2007 03:45, Gerd Hoffmann pondered: > Robin Getz wrote: > > I was putting together an early printk implementation for the Blackfin, and > > was wondering what the expected behaviour was in this situation. > > > > When I set up my bootargs earlyprintk=serial,ttyBF0,57600 and have no

Re: Early printk behaviour

2007-08-16 Thread Mike Frysinger
On 8/16/07, Gerd Hoffmann <[EMAIL PROTECTED]> wrote: > Robin Getz wrote: > > I was putting together an early printk implementation for the Blackfin, and > > was wondering what the expected behaviour was in this situation. > > > > When I set up my bootargs earlyprintk=serial,ttyBF0,57600 and have

Re: Early printk behaviour

2007-08-16 Thread Gerd Hoffmann
Robin Getz wrote: > I was putting together an early printk implementation for the Blackfin, and > was wondering what the expected behaviour was in this situation. > > When I set up my bootargs earlyprintk=serial,ttyBF0,57600 and have no console > defined (no graphical console, no serial

Re: Early printk behaviour

2007-08-16 Thread Gerd Hoffmann
Robin Getz wrote: I was putting together an early printk implementation for the Blackfin, and was wondering what the expected behaviour was in this situation. When I set up my bootargs earlyprintk=serial,ttyBF0,57600 and have no console defined (no graphical console, no serial console).

Re: Early printk behaviour

2007-08-16 Thread Mike Frysinger
On 8/16/07, Gerd Hoffmann [EMAIL PROTECTED] wrote: Robin Getz wrote: I was putting together an early printk implementation for the Blackfin, and was wondering what the expected behaviour was in this situation. When I set up my bootargs earlyprintk=serial,ttyBF0,57600 and have no

Re: Early printk behaviour

2007-08-16 Thread Robin Getz
On Thu 16 Aug 2007 03:45, Gerd Hoffmann pondered: Robin Getz wrote: I was putting together an early printk implementation for the Blackfin, and was wondering what the expected behaviour was in this situation. When I set up my bootargs earlyprintk=serial,ttyBF0,57600 and have no

Early printk behaviour

2007-08-15 Thread Robin Getz
I was putting together an early printk implementation for the Blackfin, and was wondering what the expected behaviour was in this situation. When I set up my bootargs earlyprintk=serial,ttyBF0,57600 and have no console defined (no graphical console, no serial console). based on the patch:

Early printk behaviour

2007-08-15 Thread Robin Getz
I was putting together an early printk implementation for the Blackfin, and was wondering what the expected behaviour was in this situation. When I set up my bootargs earlyprintk=serial,ttyBF0,57600 and have no console defined (no graphical console, no serial console). based on the patch: