re: i386 vs radeondrmkms problem - isa attachments suck

2015-03-03 Thread matthew green
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

re: i386 vs radeondrmkms problem - isa attachments suck

2015-03-03 Thread matthew green
Brian Buhrow writes: hello. Here is a very naive question. Could the vga driver be altered to not do its mapping until the Radeon, or other graphics driver, has had a chance to map and/or attach? To solve the loss of the printed copyright messages, perhaps a buffer could be

Re: i386 vs radeondrmkms problem - isa attachments suck

2015-03-03 Thread Roy Marples
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

re: i386 vs radeondrmkms problem - isa attachments suck

2015-03-03 Thread Brian Buhrow
hello. Here is a very naive question. Could the vga driver be altered to not do its mapping until the Radeon, or other graphics driver, has had a chance to map and/or attach? To solve the loss of the printed copyright messages, perhaps a buffer could be allocated, much like the