Skip to contentSkip to conversation

atyfb: 2.5.54

DISCUSSION Nico Schottelius 3 participants 7 messages Jan 5, 2003 – Jan 9, 2003 Framebuffer layer

lore
Share & tools
lore
#0 lore raw

Hello dear list!

With 2.5.54 there is something like success with my hardware. Now I get a cursor at the right position. I can't see what I type, but I see the cursor moving correctly.
After unloading atyfb the console still behaves this way, nothing changes.

Are there some options I should set ? I am currently just loading atyfb (with recognizes my card as PCI although it's AGP; seen in dmesg).

Greetings,

Nico

Signature · 3 lines
Please send your messages pgp-signed and/or pgp-encrypted (don't encrypt mails
to mailing list!). If you don't know what pgp is visit www.gnupg.org.
(public pgp key: ftp.schottelius.org/pub/familiy/nico/pgp-key)
#1 lore raw
Quoted 9 lines

With 2.5.54 there is something like success with my hardware. Now I get a cursor at the right position. I can't see what I type, but I see the cursor moving correctly.
After unloading atyfb the console still behaves this way, nothing changes.

Are there some options I should set ? I am currently just loading atyfb (with recognizes my card as PCI although it's AGP; seen in dmesg).

Can do post your dmesg.

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

#2 lore raw
Quoted 10 lines · James Simmons
Quoted 8 lines

With 2.5.54 there is something like success with my hardware. Now I get a cursor at the right position. I can't see what I type, but I see the cursor moving correctly.
After unloading atyfb the console still behaves this way, nothing changes.

Are there some options I should set ? I am currently just loading atyfb (with recognizes my card as PCI although it's AGP; seen in dmesg).

Can do post your dmesg.

Atyfb is known not to work on some Rage Mobility P/M (incl. the one in my Vaio :-(

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

#3 lore raw
Quoted 3 lines

Atyfb is known not to work on some Rage Mobility P/M (incl. the one in my Vaio :-(

A have a few patchs for atyfb that I haven't got around to applying just yet. One is Popov non BIOS patch for some cards. I have another patch for a new DAC for older MACH 64 cards. The big issue I like to see solved is to us ethe hardware cursor. Right now I have it disabled, its using soft_cursor. I haven't had the time to look at teh specs for how the data is layed out for the cursor image. We have in atyfb.h

struct aty_cursor {
	u8 bits[8][64];
	u8 mask[8][64];
	u8 *ram;
}

This is really weird. I like to translate to the new api.

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

#4 lore raw
Quoted 10 lines · James Simmons
Quoted 2 lines

Atyfb is known not to work on some Rage Mobility P/M (incl. the one in my Vaio :-(

A have a few patchs for atyfb that I haven't got around to applying just yet. One is Popov non BIOS patch for some cards. I have another patch for a new DAC for older MACH 64 cards. The big issue I like to see solved is to us ethe hardware cursor. Right now I have it disabled, its using soft_cursor. I haven't had the time to look at teh specs for how the data is layed out for the cursor image. We have in atyfb.h

Quoted 7 lines
struct aty_cursor {
	u8 bits[8][64];
	u8 mask[8][64];
	u8 *ram;
}

This is really weird. I like to translate to the new api.

Each pixel in the Mach64 cursor has 4 possible values: transparent, inverting, color0, or color1. It's size is 64x64, i.e. 64 rows of 8 bits per plane.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

#5 lore raw
In reply to Geert Uytterhoeven

Geert Uytterhoeven [Tue, Jan 07, 2003 at 10:58:25PM +0100]:

Quoted 2 lines

Atyfb is known not to work on some Rage Mobility P/M (incl. the one in my Vaio :-(

I hope this changes soon ;)

Nico

#6 lore raw
In reply to James Simmons

James Simmons [Tue, Jan 07, 2003 at 09:54:51PM +0000]:

Quoted 11 lines
Quoted 9 lines

With 2.5.54 there is something like success with my hardware. Now I get a cursor at the right position. I can't see what I type, but I see the cursor moving correctly.
After unloading atyfb the console still behaves this way, nothing changes.

Are there some options I should set ? I am currently just loading atyfb (with recognizes my card as PCI although it's AGP; seen in dmesg).

Can do post your dmesg.

!dmesg

atyfb: 3D RAGE Mobility (PCI) [0x4c4d rev 0x64] 8M SDRAM, 29.498928 MHz XTAL, 230 MHz PLL, 50 Mhz MCLK
fb0: ATY Mach64 frame buffer device on PCI

Just tell me, if you need more information.

Nico