This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-1480625894-1156420596=:937
Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

On Thu, 24 Aug 2006, Jared D. McNeill wrote:

> There is an outstanding issue here in wsdisplay around this very issue --=
 if=20
> I allow vga to attach early and claim to be the console later on, wsdispl=
ay=20
> loses in a DIAGNOSTIC kernel. wsdisplay_cnattach is allowed to be called=
=20
> exactly once. This needs to be modified (macallan@ has patches) to allow =
it=20
> to be called up to two times.

 =09OK.

>> vesabios0 at mainbus0: version 1.2, =EF=BF=BD=EF=BF=BD =EF=BF=BD=EF=BF=
=BD
>> vesafb0 at vesabios0: VESA frame buffer
>> vesafb0: no supported mode found
>> text at vesabios0 not configured
>
> VESA BIOS extensions >=3D 2.0 are required for vesafb. vesabios probably=
=20
> shouldn't bother attaching a vesafb if the version is too low.

 =09That seems pretty reasonable and I'd expect that to catch most
 =09of the falure cases :)


--=20
 =09=09David/absolute       -- www.NetBSD.org: No hype required --
--0-1480625894-1156420596=:937--