On Fri, 2007-01-26 at 18:10 -0800, David Miller wrote:
Adding proper support for the e10K console would be a nice
easy sparc64 kernel project for someone who wants to get
involved and has access to such a machine.
I am ready to provide access to any kernel developer or other who uses
it for
On Sat, 2007-01-27 at 12:17 +0100, Jan Engelhardt wrote:
Looking at init/main.c:
if (sys_open((const char __user *) /dev/console, O_RDWR, 0) 0)
printk(KERN_WARNING Warning: unable to open an initial console.\n);
That looks almost like a bug :-/
/dev/console will decay into a pointer
On Jan 27 2007 09:37, Tom 'spot' Callaway wrote:
int ret = sys_open((const char __user *)/dev/console, O_RDWR, 0);
if(ret 0)
printk(KERN_WARNING Warning: unable to open an
initial console (%d)\n, ret);
I wonder what return code it will give (-EFAULT is my guess).
Warning:
From: Jan Engelhardt [EMAIL PROTECTED]
Date: Sat, 27 Jan 2007 12:17:53 +0100 (MET)
Looking at init/main.c:
if (sys_open((const char __user *) /dev/console, O_RDWR, 0) 0)
printk(KERN_WARNING Warning: unable to open an initial console.\n);
That looks almost like a bug :-/
Heyo!
I hate to bring this one up again, but it seems that I'm not the only one
suffering from this problem..
There still seems to be issues with gcc 4.1 atyfb driver and this time I'm
sure it's not only related to my own gcc release as I've seen it being
reproduced on both aurora and
