Is the ignoring of attach priority a general characteristic of
indirect buses, and might it make sense for config to be able to
explicitly prioritise the order the cfdata[] entries? I know uebayasi@
has been rototilling config and wondered if he could be interested...
:)
The problem
delayed console isn't a bad
idea -- i'd like to be able to have multiple console output as well,
like linux has provided with 'console=vga console=com1' since at
least 2.4 days...
.mrg.
Thoughts?
-Brian
On Mar 4, 9:10am, matthew green wrote:
} Subject: re: i386 vs radeondrmkms problem - isa
On Wednesday 04 Mar 2015 12:28:25 matthew green wrote:
i think the diagnostic benefit of having console messages appear as
soon as they're printed is too important to give up.
Agree 100% as a kernel hacker on i386 with a radeon!
Roy
serial ports. I've thought about trying
something like this, but haven't gotten frustrated enough yet to do it.
Thoughts?
-Brian
On Mar 4, 9:10am, matthew green wrote:
} Subject: re: i386 vs radeondrmkms problem - isa attachments suck
}
} Is the ignoring of attach priority a general
a...@absd.org (David Brownlee) writes:
Is the ignoring of attach priority a general characteristic of
indirect buses, and might it make sense for config to be able to
explicitly prioritise the order the cfdata[] entries? I know uebayasi@
has been rototilling config and wondered if he could be
On Mon, Mar 02, 2015 at 01:08:04PM +, David Brownlee wrote:
On 28 February 2015 at 09:44, matthew green m...@eterna.com.au wrote:
hi folks.
i've been trying to find a least-ugly solution to the radeondrmkms
on i386 problem. quick summary of what's wrong:
radeondrmkms
On 28 February 2015 at 09:44, matthew green m...@eterna.com.au wrote:
hi folks.
i've been trying to find a least-ugly solution to the radeondrmkms
on i386 problem. quick summary of what's wrong:
radeondrmkms doesn't complete attachments (and most
importantly create a
hi folks.
i've been trying to find a least-ugly solution to the radeondrmkms
on i386 problem. quick summary of what's wrong:
radeondrmkms doesn't complete attachments (and most
importantly create a wsdisplay) until mountroot completes.
this means it happens quite late
Date: Sat, 28 Feb 2015 11:36:18 +0100
From: Martin Husemann mar...@duskware.de
The need for loaded firmware from the filesystem at console attach time
sounds like a seriously bad idea to me.
Agree. But that's not the only issue mrg@ mentioned -- even if radeon
actually attaches
Date: Sun, 01 Mar 2015 00:31:55 +1100
from: matthew green m...@eterna.com.au
The need for loaded firmware from the filesystem at console attach time
sounds like a seriously bad idea to me.
Agree. But that's not the only issue mrg@ mentioned -- even if radeon
The need for loaded firmware from the filesystem at console attach time
sounds like a seriously bad idea to me.
If the radeondrmkmsfs driver would provide plain old text console, and only
after loading the firmware would gain the ability to switch the fb into X
mode, everything else would become
11 matches
Mail list logo
