-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Feb 12, 2007, at 19:21, leon zadorin wrote:

> On 2/11/07, Michael Lorenz <macallan@netbsd.org> wrote:
>> Hmm, I use xterm-color as terminal type, it seems to match wsdisplay's
>> capabilities far better than vt100 ( which does no colour ) or vt220 (
>> wsdisplay doesn't understand all its control codes - just open a .c
>> file in pkgsrc/editors/joe and watch the botched syntax highlighting -
>> works fine with xterm-color )
>
> also very strange :-) I have tried (setting "/etc/ttys" term's type to
> "xterm-color") and it did not work (still no reverse text - I will try
> again to "double check" :-)

Well, echo $TERM will tell you :)

> just to make sure we are on the same wavelength:
> 1) we both have tried it with radeonfb driver and
> 2) we are running in conlose mode (i.e. not in the X server)... right?

Yes. Machfb and chipfb behave the same way. They only differ in the 
exact way to feed character bitmaps into the graphics chip - they all 
advertise the same capabilities and use more or less identical 
character drawing functions.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRdFcYcpnzkX8Yg2nAQLn7QgAtD34e7k6XOttUTVlzeN0GCJS2F+tVkd0
cVWl7wcvh2w9O4E1iQJpm9j2S2JHZJnqG/IlYSfUZMN5KpRq+I8BJ0ec51Z6SSNj
v0ZQlcmyGU3wWqnARjIPmXrMBMzHePqX1qgvcz1oQFdzwJuS4dXBdlZrwQnucgGm
udFBPBEpZpmPDV7AhaSge5JqwrDZAbcwcCRkXIXdJFd3whlFMTDH1NE3a7dnOKxL
tRyPgeNgb9KJVEzWekyYQ05Ht5AyaccvLPzKg5ZOGYER9BFRc9XTNvRUCG54c/lr
O8m1SKDpBOwOk9MeEDP0fUOjD9jcBF+1c7HY4rNk0DkMQ4ij0j493A==
=Iuod
-----END PGP SIGNATURE-----