Menu
▾
▴
linux-fbdev-devel — linux-fbdev mailing list for project developers
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
(1) |
Apr
(104) |
May
(81) |
Jun
(248) |
Jul
(133) |
Aug
(33) |
Sep
(53) |
Oct
(82) |
Nov
(166) |
Dec
(71) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(121) |
Feb
(42) |
Mar
(39) |
Apr
(84) |
May
(87) |
Jun
(58) |
Jul
(97) |
Aug
(130) |
Sep
(32) |
Oct
(139) |
Nov
(108) |
Dec
(216) |
| 2003 |
Jan
(299) |
Feb
(136) |
Mar
(392) |
Apr
(141) |
May
(137) |
Jun
(107) |
Jul
(94) |
Aug
(262) |
Sep
(300) |
Oct
(216) |
Nov
(72) |
Dec
(94) |
| 2004 |
Jan
(174) |
Feb
(192) |
Mar
(215) |
Apr
(314) |
May
(319) |
Jun
(293) |
Jul
(205) |
Aug
(161) |
Sep
(192) |
Oct
(226) |
Nov
(308) |
Dec
(89) |
| 2005 |
Jan
(127) |
Feb
(269) |
Mar
(588) |
Apr
(106) |
May
(77) |
Jun
(77) |
Jul
(161) |
Aug
(239) |
Sep
(86) |
Oct
(112) |
Nov
(153) |
Dec
(145) |
| 2006 |
Jan
(87) |
Feb
(57) |
Mar
(129) |
Apr
(109) |
May
(102) |
Jun
(232) |
Jul
(97) |
Aug
(69) |
Sep
(67) |
Oct
(69) |
Nov
(214) |
Dec
(82) |
| 2007 |
Jan
(133) |
Feb
(307) |
Mar
(121) |
Apr
(171) |
May
(229) |
Jun
(156) |
Jul
(185) |
Aug
(160) |
Sep
(122) |
Oct
(130) |
Nov
(78) |
Dec
(27) |
| 2008 |
Jan
(105) |
Feb
(137) |
Mar
(146) |
Apr
(148) |
May
(239) |
Jun
(208) |
Jul
(157) |
Aug
(244) |
Sep
(119) |
Oct
(125) |
Nov
(189) |
Dec
(225) |
| 2009 |
Jan
(157) |
Feb
(139) |
Mar
(106) |
Apr
(130) |
May
(246) |
Jun
(189) |
Jul
(128) |
Aug
(127) |
Sep
(88) |
Oct
(86) |
Nov
(216) |
Dec
(9) |
| 2010 |
Jan
(5) |
Feb
|
Mar
(11) |
Apr
(31) |
May
(3) |
Jun
|
Jul
(7) |
Aug
|
Sep
(1) |
Oct
|
Nov
(1) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Sven L. <lu...@dp...> - 2002-11-27 07:27:25
|
On Tue, Nov 26, 2002 at 11:38:04PM +0000, James Simmons wrote: > > > I have plans for doing a full rewrite of pm3fb for 2.5, just not really > > the times right now. I will do it before 2.6 (or 3.0 or whatever) is > > released though. I have already done some work, just not filled in the > > mode changes and other such. That said, it may be on the limit of my > > NDA, which was supposed to be for XFree86 only (altough i guess the > > current XFree86 code counts as available from other source though. > > I just finished the low level driver api. It pretty much is set in stone. > I might remove fg_color and bg_color in struct fb_image but that is a > maybe and a small issue. I'm going to add software rotation in tonight. > Then after that start cleaning up fbcon.c itself. You can grab the latest > patch against 2.5.49 at > > http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz > > It works and several drivers work. Ok, thanks, i will give it a try. But right now, i am doing some XFree86 work that need to be finished before (or shortly after) the 4.3.0 feature freeze. Friendly, Sven Luther |
|
From: James S. <jsi...@in...> - 2002-11-27 00:53:31
|
> The proper fix for pm3fb in 2.5 is to delete it, at least > until someone else rewrite it or until 2.5.x can actually > compile and work on PowerPC and I can rewrite it myself. Does the ppc BK tree work? |
|
From: James S. <jsi...@in...> - 2002-11-27 00:37:31
|
> I've been doing some unsuccessful Googling for programmer's documentation > on the CGsix. Anyone has any URLs handy? As in the sparc CGsix framebuffer device? I think I know where I can get docs on that. |
|
From: James S. <jsi...@in...> - 2002-11-26 23:58:54
|
> --- linux-2.5.49/drivers/video/aty128fb.c.old 2002-08-27 19:11:02.000000000 -0500 > +++ linux-2.5.49/drivers/video/aty128fb.c 2002-11-22 19:56:35.000000000 -0600 Updated to new api. Those structs are gone. > --- linux-2.5.49/drivers/video/controlfb.c.old 2002-08-27 19:11:02.000000000 -0500 > +++ linux-2.5.49/drivers/video/controlfb.c 2002-11-22 19:56:20.000000000 -0600 Have to look. It has been updated but I don't have hardware to test it. I think those structs are gone. > +++ linux-2.5.49/drivers/video/fbcon-afb.c 2002-11-22 19:56:18.000000000 [snip] All fbcon-*.c files are gone. The framebuffer console is now acceleration driven via fillrect, copyarea, and image blits. > +++ linux-2.5.49/drivers/video/g364fb.c 2002-11-23 10:03:25.000000000 -0600 Applied. > +++ linux-2.5.49/drivers/video/neofb.c 2002-11-22 19:56:18.000000000 -0600 Been applied for awhile. > +++ linux-2.5.49/drivers/video/pm2fb.c 2002-11-22 19:56:39.000000000 -0600 Being rewritten to new api. > --- linux-2.5.49/drivers/video/retz3fb.c.old 2002-08-27 19:11:03.000000000 -0500 Needs to ported to new api. The aty128 driver also needs a few updates to C99. I will do that tonight. |
|
From: James S. <jsi...@in...> - 2002-11-26 23:40:58
|
Do you have a latest driver? My co work has a laptop with a trident card that I can work on. I will help port it over to the final api. |
|
From: James S. <jsi...@in...> - 2002-11-26 23:39:27
|
> I have plans for doing a full rewrite of pm3fb for 2.5, just not really > the times right now. I will do it before 2.6 (or 3.0 or whatever) is > released though. I have already done some work, just not filled in the > mode changes and other such. That said, it may be on the limit of my > NDA, which was supposed to be for XFree86 only (altough i guess the > current XFree86 code counts as available from other source though. I just finished the low level driver api. It pretty much is set in stone. I might remove fg_color and bg_color in struct fb_image but that is a maybe and a small issue. I'm going to add software rotation in tonight. Then after that start cleaning up fbcon.c itself. You can grab the latest patch against 2.5.49 at http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz It works and several drivers work. |
|
From: James S. <jsi...@in...> - 2002-11-26 23:23:17
|
> > Hm. Strange. It should work. Can you get serial console working? > > Forgot to mention, I've seen message: > fbcon_setup: No support for fontwidth 8 > in /var/log/dmesg. > > I found this printk() in fbcon_setup(), but i can't even imagine > why it happens. Perfect. I found the problem and I'm about to commit to BK. I posted the latest patch against 2.5.49 at http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz > I understand this situation perfectly, looks like it's almost common for > developers working in "not so importatnt for servers" subsystems :( :-( Some day that attitude will change. P.S Several drivers have been ported but not all. NVIDIA is still broken but I will fix it tonight. |
|
From: James S. <jsi...@in...> - 2002-11-26 20:44:39
|
Hi! Here is the patch I promised. It is against 2.5.49. Note fbcon is broken. I haven't found the problem yet since using modules is really broken. I started to work on making fbcon modular. Several driver have been updated to the latest changes in the api. THe api is pretty much rock solid now. You can grab the patch at http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz Let me know how it goes. P.S I didn't annouce it on lkml yet because fbcon is broken. Once it is fixed I will push what we have to linus. |
|
From: <ma...@mm...> - 2002-11-26 19:57:40
|
hi,
The following is against 2.5 current and fixes an timer
warning I'm getting during boot.
Mathijs
diff -Nru a/drivers/video/fbcon.c b/drivers/video/fbcon.c
--- a/drivers/video/fbcon.c Wed Nov 27 10:42:53 2002
+++ b/drivers/video/fbcon.c Wed Nov 27 10:42:54 2002
@@ -230,9 +230,8 @@
static void cursor_timer_handler(unsigned long dev_addr);
-static struct timer_list cursor_timer = {
- function: cursor_timer_handler
-};
+static struct timer_list cursor_timer =
+ TIMER_INITIALIZER(cursor_timer_handler, 0, 0);
static void cursor_timer_handler(unsigned long dev_addr)
{
|
|
From: Antonino D. <ad...@po...> - 2002-11-26 01:55:38
|
Hi, I happened to find my old Riva128 card and tried the rivafb driver. Noticed that color (and the logo)is wrong at > 8bpp. Looking at the code, it exports the visual as FB_VISUAL_DIRECTCOLOR at 16 and 32 bpp, but the DAC was not set up as such. Also the palette is set up as Truecolor. What I found interesting was that accessing the framebuffer directly, the pixel must be in directcolor (with a properly configured DAC) but using the accel functions, the pixel value that is passed must be in truecolor format. I'm not sure if this is true for all NV hardware, but I'm attaching a patch that fixed this problem for the Riva 128 at least. If no other archs are affected, I'll fix the patch to be specific for NV_ARCH_03 only. (patch is against 2.4.19) Tony PS: James, While doing this, I was able to modify the rivafb 2.5 driver and included hardware supported drawing functions. I'm planning to port the hardware cursor as well. You may wish to work with other cards then. (Ani, only if you don't mind -- since I'm planning to revive an old box using the Riva card and rivafb) |
|
From: James S. <jsi...@in...> - 2002-11-26 00:41:01
|
> For what it's worth, the interleaved modes on atari works like this: > > The bitplanes are interleaved on 16 bit big-endian word basis so if you > have two bitplanes, bit 0 of the first 16 pixels would be in the first > 16 bit word in the display memory, bit 1 of the first 16 pixels would be > in the second word. With bit 0 I mean as masked out by & 0x0001 in C, > and bit 1 as masked out by 0x0002. > > The Atari ST line support three resolutions by default: > 320x200 4 bit planes > 640x200 2 bit planes > 640x400 1 bit plane Okay I have been think about the other modes and can't figure out how they would work. Could you do a run down to get my hamster running? |
|
From: Art H. <ah...@ai...> - 2002-11-25 22:44:28
|
Hi.
Here's a set of patches switching drivers/video to use C99 initializers.
The patches are against 2.5.49.
Art Haas
--- linux-2.5.49/drivers/video/aty128fb.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/aty128fb.c 2002-11-22 19:56:35.000000000 -0600
@@ -2397,14 +2397,14 @@
}
static struct display_switch fbcon_aty128_8 = {
- setup: fbcon_cfb8_setup,
- bmove: fbcon_aty128_bmove,
- clear: fbcon_cfb8_clear,
- putc: fbcon_aty8_putc,
- putcs: fbcon_aty8_putcs,
- revc: fbcon_cfb8_revc,
- clear_margins: fbcon_aty8_clear_margins,
- fontwidthmask: FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
+ .setup = fbcon_cfb8_setup,
+ .bmove = fbcon_aty128_bmove,
+ .clear = fbcon_cfb8_clear,
+ .putc = fbcon_aty8_putc,
+ .putcs = fbcon_aty8_putcs,
+ .revc = fbcon_cfb8_revc,
+ .clear_margins = fbcon_aty8_clear_margins,
+ .fontwidthmask = FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
};
#endif
#ifdef FBCON_HAS_CFB16
@@ -2445,14 +2445,14 @@
}
static struct display_switch fbcon_aty128_16 = {
- setup: fbcon_cfb16_setup,
- bmove: fbcon_aty128_bmove,
- clear: fbcon_cfb16_clear,
- putc: fbcon_aty16_putc,
- putcs: fbcon_aty16_putcs,
- revc: fbcon_cfb16_revc,
- clear_margins: fbcon_aty16_clear_margins,
- fontwidthmask: FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
+ .setup = fbcon_cfb16_setup,
+ .bmove = fbcon_aty128_bmove,
+ .clear = fbcon_cfb16_clear,
+ .putc = fbcon_aty16_putc,
+ .putcs = fbcon_aty16_putcs,
+ .revc = fbcon_cfb16_revc,
+ .clear_margins = fbcon_aty16_clear_margins,
+ .fontwidthmask = FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
};
#endif
#ifdef FBCON_HAS_CFB24
@@ -2493,14 +2493,14 @@
}
static struct display_switch fbcon_aty128_24 = {
- setup: fbcon_cfb24_setup,
- bmove: fbcon_aty128_bmove,
- clear: fbcon_cfb24_clear,
- putc: fbcon_aty24_putc,
- putcs: fbcon_aty24_putcs,
- revc: fbcon_cfb24_revc,
- clear_margins: fbcon_aty24_clear_margins,
- fontwidthmask: FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
+ .setup = fbcon_cfb24_setup,
+ .bmove = fbcon_aty128_bmove,
+ .clear = fbcon_cfb24_clear,
+ .putc = fbcon_aty24_putc,
+ .putcs = fbcon_aty24_putcs,
+ .revc = fbcon_cfb24_revc,
+ .clear_margins = fbcon_aty24_clear_margins,
+ .fontwidthmask = FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
};
#endif
#ifdef FBCON_HAS_CFB32
@@ -2541,14 +2541,14 @@
}
static struct display_switch fbcon_aty128_32 = {
- setup: fbcon_cfb32_setup,
- bmove: fbcon_aty128_bmove,
- clear: fbcon_cfb32_clear,
- putc: fbcon_aty32_putc,
- putcs: fbcon_aty32_putcs,
- revc: fbcon_cfb32_revc,
- clear_margins: fbcon_aty32_clear_margins,
- fontwidthmask: FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
+ .setup = fbcon_cfb32_setup,
+ .bmove = fbcon_aty128_bmove,
+ .clear = fbcon_cfb32_clear,
+ .putc = fbcon_aty32_putc,
+ .putcs = fbcon_aty32_putcs,
+ .revc = fbcon_cfb32_revc,
+ .clear_margins = fbcon_aty32_clear_margins,
+ .fontwidthmask = FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
};
#endif
--- linux-2.5.49/drivers/video/controlfb.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/controlfb.c 2002-11-22 19:56:20.000000000 -0600
@@ -1264,25 +1264,25 @@
}
static struct display_switch control_cfb16 = {
- setup: fbcon_cfb16_setup,
- bmove: fbcon_cfb16_bmove,
- clear: fbcon_cfb16_clear,
- putc: fbcon_cfb16_putc,
- putcs: fbcon_cfb16_putcs,
- revc: control_cfb16_revc,
- clear_margins: fbcon_cfb16_clear_margins,
- fontwidthmask: FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
+ .setup = fbcon_cfb16_setup,
+ .bmove = fbcon_cfb16_bmove,
+ .clear = fbcon_cfb16_clear,
+ .putc = fbcon_cfb16_putc,
+ .putcs = fbcon_cfb16_putcs,
+ .revc = control_cfb16_revc,
+ .clear_margins = fbcon_cfb16_clear_margins,
+ .fontwidthmask = FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
};
static struct display_switch control_cfb32 = {
- setup: fbcon_cfb32_setup,
- bmove: fbcon_cfb32_bmove,
- clear: fbcon_cfb32_clear,
- putc: fbcon_cfb32_putc,
- putcs: fbcon_cfb32_putcs,
- revc: control_cfb32_revc,
- clear_margins: fbcon_cfb32_clear_margins,
- fontwidthmask: FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
+ .setup = fbcon_cfb32_setup,
+ .bmove = fbcon_cfb32_bmove,
+ .clear = fbcon_cfb32_clear,
+ .putc = fbcon_cfb32_putc,
+ .putcs = fbcon_cfb32_putcs,
+ .revc = control_cfb32_revc,
+ .clear_margins = fbcon_cfb32_clear_margins,
+ .fontwidthmask = FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
};
--- linux-2.5.49/drivers/video/fbcon-afb.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-afb.c 2002-11-22 19:56:18.000000000 -0600
@@ -412,13 +412,13 @@
*/
struct display_switch fbcon_afb = {
- setup: fbcon_afb_setup,
- bmove: fbcon_afb_bmove,
- clear: fbcon_afb_clear,
- putc: fbcon_afb_putc,
- putcs: fbcon_afb_putcs,
- revc: fbcon_afb_revc,
- fontwidthmask: FONTWIDTH(8)
+ .setup = fbcon_afb_setup,
+ .bmove = fbcon_afb_bmove,
+ .clear = fbcon_afb_clear,
+ .putc = fbcon_afb_putc,
+ .putcs = fbcon_afb_putcs,
+ .revc = fbcon_afb_revc,
+ .fontwidthmask = FONTWIDTH(8)
};
--- linux-2.5.49/drivers/video/fbcon-cfb16.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-cfb16.c 2002-11-23 10:00:17.000000000 -0600
@@ -281,14 +281,14 @@
*/
struct display_switch fbcon_cfb16 = {
- setup: fbcon_cfb16_setup,
- bmove: fbcon_cfb16_bmove,
- clear: fbcon_cfb16_clear,
- putc: fbcon_cfb16_putc,
- putcs: fbcon_cfb16_putcs,
- revc: fbcon_cfb16_revc,
- clear_margins: fbcon_cfb16_clear_margins,
- fontwidthmask: FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
+ .setup = fbcon_cfb16_setup,
+ .bmove = fbcon_cfb16_bmove,
+ .clear = fbcon_cfb16_clear,
+ .putc = fbcon_cfb16_putc,
+ .putcs = fbcon_cfb16_putcs,
+ .revc = fbcon_cfb16_revc,
+ .clear_margins = fbcon_cfb16_clear_margins,
+ .fontwidthmask = FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
};
--- linux-2.5.49/drivers/video/fbcon-cfb2.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-cfb2.c 2002-11-23 10:00:54.000000000 -0600
@@ -189,13 +189,13 @@
*/
struct display_switch fbcon_cfb2 = {
- setup: fbcon_cfb2_setup,
- bmove: fbcon_cfb2_bmove,
- clear: fbcon_cfb2_clear,
- putc: fbcon_cfb2_putc,
- putcs: fbcon_cfb2_putcs,
- revc: fbcon_cfb2_revc,
- fontwidthmask: FONTWIDTH(8)
+ .setup = fbcon_cfb2_setup,
+ .bmove = fbcon_cfb2_bmove,
+ .clear = fbcon_cfb2_clear,
+ .putc = fbcon_cfb2_putc,
+ .putcs = fbcon_cfb2_putcs,
+ .revc = fbcon_cfb2_revc,
+ .fontwidthmask = FONTWIDTH(8)
};
--- linux-2.5.49/drivers/video/fbcon-cfb24.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-cfb24.c 2002-11-22 19:56:23.000000000 -0600
@@ -295,14 +295,14 @@
*/
struct display_switch fbcon_cfb24 = {
- setup: fbcon_cfb24_setup,
- bmove: fbcon_cfb24_bmove,
- clear: fbcon_cfb24_clear,
- putc: fbcon_cfb24_putc,
- putcs: fbcon_cfb24_putcs,
- revc: fbcon_cfb24_revc,
- clear_margins: fbcon_cfb24_clear_margins,
- fontwidthmask: FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
+ .setup = fbcon_cfb24_setup,
+ .bmove = fbcon_cfb24_bmove,
+ .clear = fbcon_cfb24_clear,
+ .putc = fbcon_cfb24_putc,
+ .putcs = fbcon_cfb24_putcs,
+ .revc = fbcon_cfb24_revc,
+ .clear_margins = fbcon_cfb24_clear_margins,
+ .fontwidthmask = FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
};
--- linux-2.5.49/drivers/video/fbcon-cfb32.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-cfb32.c 2002-11-22 19:56:20.000000000 -0600
@@ -267,14 +267,14 @@
*/
struct display_switch fbcon_cfb32 = {
- setup: fbcon_cfb32_setup,
- bmove: fbcon_cfb32_bmove,
- clear: fbcon_cfb32_clear,
- putc: fbcon_cfb32_putc,
- putcs: fbcon_cfb32_putcs,
- revc: fbcon_cfb32_revc,
- clear_margins: fbcon_cfb32_clear_margins,
- fontwidthmask: FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
+ .setup = fbcon_cfb32_setup,
+ .bmove = fbcon_cfb32_bmove,
+ .clear = fbcon_cfb32_clear,
+ .putc = fbcon_cfb32_putc,
+ .putcs = fbcon_cfb32_putcs,
+ .revc = fbcon_cfb32_revc,
+ .clear_margins = fbcon_cfb32_clear_margins,
+ .fontwidthmask = FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
};
--- linux-2.5.49/drivers/video/fbcon-cfb4.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-cfb4.c 2002-11-23 10:01:12.000000000 -0600
@@ -193,13 +193,13 @@
*/
struct display_switch fbcon_cfb4 = {
- setup: fbcon_cfb4_setup,
- bmove: fbcon_cfb4_bmove,
- clear: fbcon_cfb4_clear,
- putc: fbcon_cfb4_putc,
- putcs: fbcon_cfb4_putcs,
- revc: fbcon_cfb4_revc,
- fontwidthmask: FONTWIDTH(8)
+ .setup = fbcon_cfb4_setup,
+ .bmove = fbcon_cfb4_bmove,
+ .clear = fbcon_cfb4_clear,
+ .putc = fbcon_cfb4_putc,
+ .putcs = fbcon_cfb4_putcs,
+ .revc = fbcon_cfb4_revc,
+ .fontwidthmask = FONTWIDTH(8)
};
--- linux-2.5.49/drivers/video/fbcon-cfb8.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-cfb8.c 2002-11-23 10:01:44.000000000 -0600
@@ -256,14 +256,14 @@
*/
struct display_switch fbcon_cfb8 = {
- setup: fbcon_cfb8_setup,
- bmove: fbcon_cfb8_bmove,
- clear: fbcon_cfb8_clear,
- putc: fbcon_cfb8_putc,
- putcs: fbcon_cfb8_putcs,
- revc: fbcon_cfb8_revc,
- clear_margins: fbcon_cfb8_clear_margins,
- fontwidthmask: FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
+ .setup = fbcon_cfb8_setup,
+ .bmove = fbcon_cfb8_bmove,
+ .clear = fbcon_cfb8_clear,
+ .putc = fbcon_cfb8_putc,
+ .putcs = fbcon_cfb8_putcs,
+ .revc = fbcon_cfb8_revc,
+ .clear_margins = fbcon_cfb8_clear_margins,
+ .fontwidthmask = FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16)
};
--- linux-2.5.49/drivers/video/fbcon-ilbm.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-ilbm.c 2002-11-22 19:56:28.000000000 -0600
@@ -260,13 +260,13 @@
*/
struct display_switch fbcon_ilbm = {
- setup: fbcon_ilbm_setup,
- bmove: fbcon_ilbm_bmove,
- clear: fbcon_ilbm_clear,
- putc: fbcon_ilbm_putc,
- putcs: fbcon_ilbm_putcs,
- revc: fbcon_ilbm_revc,
- fontwidthmask: FONTWIDTH(8)
+ .setup = fbcon_ilbm_setup,
+ .bmove = fbcon_ilbm_bmove,
+ .clear = fbcon_ilbm_clear,
+ .putc = fbcon_ilbm_putc,
+ .putcs = fbcon_ilbm_putcs,
+ .revc = fbcon_ilbm_revc,
+ .fontwidthmask = FONTWIDTH(8)
};
--- linux-2.5.49/drivers/video/fbcon-iplan2p2.c.old 2002-07-05 18:42:32.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-iplan2p2.c 2002-11-22 19:56:45.000000000 -0600
@@ -438,14 +438,14 @@
*/
struct display_switch fbcon_iplan2p2 = {
- setup: fbcon_iplan2p2_setup,
- bmove: fbcon_iplan2p2_bmove,
- clear: fbcon_iplan2p2_clear,
- putc: fbcon_iplan2p2_putc,
- putcs: fbcon_iplan2p2_putcs,
- revc: fbcon_iplan2p2_revc,
- clear_margins: fbcon_iplan2p2_clear_margins,
- fontwidthmask: FONTWIDTH(8)
+ .setup = fbcon_iplan2p2_setup,
+ .bmove = fbcon_iplan2p2_bmove,
+ .clear = fbcon_iplan2p2_clear,
+ .putc = fbcon_iplan2p2_putc,
+ .putcs = fbcon_iplan2p2_putcs,
+ .revc = fbcon_iplan2p2_revc,
+ .clear_margins = fbcon_iplan2p2_clear_margins,
+ .fontwidthmask = FONTWIDTH(8)
};
--- linux-2.5.49/drivers/video/fbcon-iplan2p4.c.old 2002-07-05 18:42:19.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-iplan2p4.c 2002-11-22 19:56:25.000000000 -0600
@@ -459,14 +459,14 @@
*/
struct display_switch fbcon_iplan2p4 = {
- setup: fbcon_iplan2p4_setup,
- bmove: fbcon_iplan2p4_bmove,
- clear: fbcon_iplan2p4_clear,
- putc: fbcon_iplan2p4_putc,
- putcs: fbcon_iplan2p4_putcs,
- revc: fbcon_iplan2p4_revc,
- clear_margins: fbcon_iplan2p4_clear_margins,
- fontwidthmask: FONTWIDTH(8)
+ .setup = fbcon_iplan2p4_setup,
+ .bmove = fbcon_iplan2p4_bmove,
+ .clear = fbcon_iplan2p4_clear,
+ .putc = fbcon_iplan2p4_putc,
+ .putcs = fbcon_iplan2p4_putcs,
+ .revc = fbcon_iplan2p4_revc,
+ .clear_margins = fbcon_iplan2p4_clear_margins,
+ .fontwidthmask = FONTWIDTH(8)
};
--- linux-2.5.49/drivers/video/fbcon-iplan2p8.c.old 2002-07-05 18:42:20.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-iplan2p8.c 2002-11-22 19:56:28.000000000 -0600
@@ -496,14 +496,14 @@
*/
struct display_switch fbcon_iplan2p8 = {
- setup: fbcon_iplan2p8_setup,
- bmove: fbcon_iplan2p8_bmove,
- clear: fbcon_iplan2p8_clear,
- putc: fbcon_iplan2p8_putc,
- putcs: fbcon_iplan2p8_putcs,
- revc: fbcon_iplan2p8_revc,
- clear_margins: fbcon_iplan2p8_clear_margins,
- fontwidthmask: FONTWIDTH(8)
+ .setup = fbcon_iplan2p8_setup,
+ .bmove = fbcon_iplan2p8_bmove,
+ .clear = fbcon_iplan2p8_clear,
+ .putc = fbcon_iplan2p8_putc,
+ .putcs = fbcon_iplan2p8_putcs,
+ .revc = fbcon_iplan2p8_revc,
+ .clear_margins = fbcon_iplan2p8_clear_margins,
+ .fontwidthmask = FONTWIDTH(8)
};
--- linux-2.5.49/drivers/video/fbcon-mfb.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-mfb.c 2002-11-22 19:56:40.000000000 -0600
@@ -179,14 +179,14 @@
*/
struct display_switch fbcon_mfb = {
- setup: fbcon_mfb_setup,
- bmove: fbcon_mfb_bmove,
- clear: fbcon_mfb_clear,
- putc: fbcon_mfb_putc,
- putcs: fbcon_mfb_putcs,
- revc: fbcon_mfb_revc,
- clear_margins: fbcon_mfb_clear_margins,
- fontwidthmask: FONTWIDTH(8)
+ .setup = fbcon_mfb_setup,
+ .bmove = fbcon_mfb_bmove,
+ .clear = fbcon_mfb_clear,
+ .putc = fbcon_mfb_putc,
+ .putcs = fbcon_mfb_putcs,
+ .revc = fbcon_mfb_revc,
+ .clear_margins = fbcon_mfb_clear_margins,
+ .fontwidthmask = FONTWIDTH(8)
};
--- linux-2.5.49/drivers/video/fbcon-vga-planes.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/fbcon-vga-planes.c 2002-11-22 19:56:36.000000000 -0600
@@ -329,23 +329,23 @@
}
struct display_switch fbcon_vga_planes = {
- setup: fbcon_vga_planes_setup,
- bmove: fbcon_vga_planes_bmove,
- clear: fbcon_vga_planes_clear,
- putc: fbcon_vga_planes_putc,
- putcs: fbcon_vga_planes_putcs,
- revc: fbcon_vga_planes_revc,
- fontwidthmask: FONTWIDTH(8)
+ .setup = fbcon_vga_planes_setup,
+ .bmove = fbcon_vga_planes_bmove,
+ .clear = fbcon_vga_planes_clear,
+ .putc = fbcon_vga_planes_putc,
+ .putcs = fbcon_vga_planes_putcs,
+ .revc = fbcon_vga_planes_revc,
+ .fontwidthmask = FONTWIDTH(8)
};
struct display_switch fbcon_ega_planes = {
- setup: fbcon_vga_planes_setup,
- bmove: fbcon_vga_planes_bmove,
- clear: fbcon_vga_planes_clear,
- putc: fbcon_ega_planes_putc,
- putcs: fbcon_ega_planes_putcs,
- revc: fbcon_vga_planes_revc,
- fontwidthmask: FONTWIDTH(8)
+ .setup = fbcon_vga_planes_setup,
+ .bmove = fbcon_vga_planes_bmove,
+ .clear = fbcon_vga_planes_clear,
+ .putc = fbcon_ega_planes_putc,
+ .putcs = fbcon_ega_planes_putcs,
+ .revc = fbcon_vga_planes_revc,
+ .fontwidthmask = FONTWIDTH(8)
};
#ifdef MODULE
--- linux-2.5.49/drivers/video/g364fb.c.old 2002-08-27 19:11:02.000000000 -0500
+++ linux-2.5.49/drivers/video/g364fb.c 2002-11-23 10:03:25.000000000 -0600
@@ -78,30 +78,30 @@
static struct fb_info fb_info;
static struct fb_fix_screeninfo fb_fix __initdata = {
- .id = "G364 8plane",
- .smem_start = 0x40000000, /* physical address */
- .type = FB_TYPE_PACKED_PIXELS,
- .visual = FB_VISUAL_PSEUDOCOLOR,
- .ypanstep = 1,
- .accel = FB_ACCEL_NONE,
+ .id = "G364 8plane",
+ .smem_start = 0x40000000, /* physical address */
+ .type = FB_TYPE_PACKED_PIXELS,
+ .visual = FB_VISUAL_PSEUDOCOLOR,
+ .ypanstep = 1,
+ .accel = FB_ACCEL_NONE,
};
static struct fb_var_screeninfo fb_var __initdata = {
- .bits_per_pixel =8,
- .red = { 0, 8, 0 },
- green: { 0, 8, 0 },
- blue: { 0, 8, 0 },
- activate:FB_ACTIVATE_NOW,
- height: -1,
- width: -1,
- pixclock:39722,
- left_margin: 40,
- right_margin: 24,
- upper_margin: 32,
- lower_margin: 11,
- hsync_len: 96,
- vsync_len: 2,
- vmode: FB_VMODE_NONINTERLACED,
+ .bits_per_pixel = 8,
+ .red = { 0, 8, 0 },
+ .green = { 0, 8, 0 },
+ .blue = { 0, 8, 0 },
+ .activate = FB_ACTIVATE_NOW,
+ .height = -1,
+ .width = -1,
+ .pixclock = 39722,
+ .left_margin = 40,
+ .right_margin = 24,
+ .upper_margin = 32,
+ .lower_margin = 11,
+ .hsync_len = 96,
+ .vsync_len = 2,
+ .vmode = FB_VMODE_NONINTERLACED,
};
/*
--- linux-2.5.49/drivers/video/neofb.c.old 2002-08-27 19:11:03.000000000 -0500
+++ linux-2.5.49/drivers/video/neofb.c 2002-11-22 19:56:18.000000000 -0600
@@ -1403,75 +1403,75 @@
/* --------------------------------------------------------------------- */
static struct fb_var_screeninfo __devinitdata neofb_var640x480x8 = {
- accel_flags: FB_ACCELF_TEXT,
- xres: 640,
- yres: 480,
- xres_virtual: 640,
- yres_virtual: 30000,
- bits_per_pixel: 8,
- pixclock: 39722,
- left_margin: 48,
- right_margin: 16,
- upper_margin: 33,
- lower_margin: 10,
- hsync_len: 96,
- vsync_len: 2,
- vmode: FB_VMODE_NONINTERLACED
+ .accel_flags = FB_ACCELF_TEXT,
+ .xres = 640,
+ .yres = 480,
+ .xres_virtual = 640,
+ .yres_virtual = 30000,
+ .bits_per_pixel = 8,
+ .pixclock = 39722,
+ .left_margin = 48,
+ .right_margin = 16,
+ .upper_margin = 33,
+ .lower_margin = 10,
+ .hsync_len = 96,
+ .vsync_len = 2,
+ .vmode = FB_VMODE_NONINTERLACED
};
static struct fb_var_screeninfo __devinitdata neofb_var800x600x8 = {
- accel_flags: FB_ACCELF_TEXT,
- xres: 800,
- yres: 600,
- xres_virtual: 800,
- yres_virtual: 30000,
- bits_per_pixel: 8,
- pixclock: 25000,
- left_margin: 88,
- right_margin: 40,
- upper_margin: 23,
- lower_margin: 1,
- hsync_len: 128,
- vsync_len: 4,
- sync: FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
- vmode: FB_VMODE_NONINTERLACED
+ .accel_flags = FB_ACCELF_TEXT,
+ .xres = 800,
+ .yres = 600,
+ .xres_virtual = 800,
+ .yres_virtual = 30000,
+ .bits_per_pixel = 8,
+ .pixclock = 25000,
+ .left_margin = 88,
+ .right_margin = 40,
+ .upper_margin = 23,
+ .lower_margin = 1,
+ .hsync_len = 128,
+ .vsync_len = 4,
+ .sync = FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
+ .vmode = FB_VMODE_NONINTERLACED
};
static struct fb_var_screeninfo __devinitdata neofb_var1024x768x8 = {
- accel_flags: FB_ACCELF_TEXT,
- xres: 1024,
- yres: 768,
- xres_virtual: 1024,
- yres_virtual: 30000,
- bits_per_pixel: 8,
- pixclock: 15385,
- left_margin: 160,
- right_margin: 24,
- upper_margin: 29,
- lower_margin: 3,
- hsync_len: 136,
- vsync_len: 6,
- sync: FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
- vmode: FB_VMODE_NONINTERLACED
+ .accel_flags = FB_ACCELF_TEXT,
+ .xres = 1024,
+ .yres = 768,
+ .xres_virtual = 1024,
+ .yres_virtual = 30000,
+ .bits_per_pixel = 8,
+ .pixclock = 15385,
+ .left_margin = 160,
+ .right_margin = 24,
+ .upper_margin = 29,
+ .lower_margin = 3,
+ .hsync_len = 136,
+ .vsync_len = 6,
+ .sync = FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
+ .vmode = FB_VMODE_NONINTERLACED
};
#ifdef NOT_DONE
static struct fb_var_screeninfo __devinitdata neofb_var1280x1024x8 = {
- accel_flags: FB_ACCELF_TEXT,
- xres: 1280,
- yres: 1024,
- xres_virtual: 1280,
- yres_virtual: 30000,
- bits_per_pixel: 8,
- pixclock: 9260,
- left_margin: 248,
- right_margin: 48,
- upper_margin: 38,
- lower_margin: 1,
- hsync_len: 112,
- vsync_len: 3,
- sync: FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
- vmode: FB_VMODE_NONINTERLACED
+ .accel_flags = FB_ACCELF_TEXT,
+ .xres = 1280,
+ .yres = 1024,
+ .xres_virtual = 1280,
+ .yres_virtual = 30000,
+ .bits_per_pixel = 8,
+ .pixclock = 9260,
+ .left_margin = 248,
+ .right_margin = 48,
+ .upper_margin = 38,
+ .lower_margin = 1,
+ .hsync_len = 112,
+ .vsync_len = 3,
+ .sync = FB_SYNC_HOR_HIGH_ACT | FB_SYNC_VERT_HIGH_ACT,
+ .vmode = FB_VMODE_NONINTERLACED
};
#endif
--- linux-2.5.49/drivers/video/pm2fb.c.old 2002-08-27 19:11:03.000000000 -0500
+++ linux-2.5.49/drivers/video/pm2fb.c 2002-11-22 19:56:39.000000000 -0600
@@ -1451,7 +1451,7 @@
.cursor = pm2fb_cursor,
.set_font = pm2fb_set_font,
.clear_margins =pm2fb_clear_margins8,
- fontwidthmask: FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16) };
+ .fontwidthmask = FONTWIDTH(4)|FONTWIDTH(8)|FONTWIDTH(12)|FONTWIDTH(16) };
#endif /* FBCON_HAS_CFB8 */
#ifdef FBCON_HAS_CFB16
--- linux-2.5.49/drivers/video/retz3fb.c.old 2002-08-27 19:11:03.000000000 -0500
+++ linux-2.5.49/drivers/video/retz3fb.c 2002-11-22 19:56:46.000000000 -0600
@@ -1589,13 +1589,13 @@
static struct display_switch fbcon_retz3_8 = {
- setup: fbcon_cfb8_setup,
- bmove: retz3_8_bmove,
- clear: retz3_8_clear,
- putc: retz3_putc,
- putcs: retz3_putcs,
- revc: retz3_revc,
- clear_margins: retz3_clear_margins,
- fontwidthmask: FONTWIDTH(8)
+ .setup = fbcon_cfb8_setup,
+ .bmove = retz3_8_bmove,
+ .clear = retz3_8_clear,
+ .putc = retz3_putc,
+ .putcs = retz3_putcs,
+ .revc = retz3_revc,
+ .clear_margins = retz3_clear_margins,
+ .fontwidthmask = FONTWIDTH(8)
};
#endif
--
They that can give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety.
-- Benjamin Franklin, Historical Review of Pennsylvania, 1759
|
|
From: Benjamin H. <be...@ke...> - 2002-11-25 21:54:31
|
On Mon, 2002-11-25 at 15:43, Hanno B=F6ck wrote: > Hi, >=20 > I would like to test the new Kernel 2.5 because it has a lot of features = I'm really waiting for. >=20 > The only problem is that I want/need a working framebuffer. In the 2.5-re= leases, the radeonfb doesn't compile. > Is there a patch that makes it working in current 2.5-kernels? > Can you give me a download-location? > (I don't know how to use bitkeeper, so if you point me to a bitkeeper-loc= ation, please add a description how I can get things from there) Get the version in the PPC tree, it should work (ppc.bkbits.net/linuxppc-2.5) Ben. |
|
From: Johan B. <jo...@no...> - 2002-11-25 21:44:11
|
m=E5n 2002-11-25 klockan 19.47 skrev James Simmons: >=20 > > > Geert is busy porting the Amigia driver to the new api. That means al= l the=20 > > > ilbm, iplan stuff will go away :-)=20 > >=20 > > I have first code for amifb, but it doesn't work yet, due to other prob= lems > > with 2.5.x on Amiga. I hope to fix these tomorrow... >=20 > Yeah!!! >=20 > > Besides, we still need someone to take care of the Atari 2-byte interle= aved > > bitplanes (iplan2p*), since I don't have the hardware, and am not 100% = sure=20 > > how they work. But reviving 2.5.x on Atari will be even harder... For what it's worth, the interleaved modes on atari works like this: The bitplanes are interleaved on 16 bit big-endian word basis so if you have two bitplanes, bit 0 of the first 16 pixels would be in the first 16 bit word in the display memory, bit 1 of the first 16 pixels would be in the second word. With bit 0 I mean as masked out by & 0x0001 in C, and bit 1 as masked out by 0x0002. The Atari ST line support three resolutions by default: 320x200 4 bit planes 640x200 2 bit planes 640x400 1 bit plane The Atari Falcon has a programmable clock so many resolutions are possible and it also features a 8 bit planes mode and 16 bit high colour mode. P.S. I don't have any Atari hardware myself anymore. > Me neither. But there is a way to find out. A trick I used to figure=20 > out the hga framebuffer lay out. Build just the fbdev layer without fbcon= .=20 > Then do a write to /dev/fbX to see what happens.=20 > The way I have fbdev now is when you open /dev/fb0 the hardware mode i= s=20 > set. When you close the /dev/fb the hardware goes back to text mode. I di= d=20 > it this way so you could insmod the driver and NOT change the hardware=20 > state. Also fb_open is the function register_framebuffer needs just befor= e=20 > take_over_console happens. The other benifiet is if X dies that uses=20 > /dev/fb to set it modes then the file will be closed automatically and te= h=20 > hardware state will be set to a sane state. This is for the case of vgaco= n=20 > with fbdev. WHat about from fbco? Well that is easy since fb_open passes = a=20 > falg to let us knwo if it is from userland for fbcon. >=20 > P.S > It appears fbcon is totally broken in BK. I'm using the above trick to= =20 > test the code. Tonight I'm going to work on making fbcon completely=20 > modular. Yeah!!!! >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Get the new Palm Tungsten T=20 > handheld. Power & Color in a compact size!=20 > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > _______________________________________________ > Linux-fbdev-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel |
|
From: Jim H. <jim...@ac...> - 2002-11-25 18:48:25
|
I'm going to make some time to move the pm2fb driver to 2.5. It'd be helpful if I could find some Permedia2 programming docs. Google can't find any, and requests to 3Dlabs have failed to elicit any response.... -- Jim Hague - jim...@in... (Work), ji...@be... (Play) Never trust a computer you can't lift or you don't control. |
|
From: James S. <jsi...@in...> - 2002-11-25 18:48:23
|
> > Geert is busy porting the Amigia driver to the new api. That means all the > > ilbm, iplan stuff will go away :-) > > I have first code for amifb, but it doesn't work yet, due to other problems > with 2.5.x on Amiga. I hope to fix these tomorrow... Yeah!!! > Besides, we still need someone to take care of the Atari 2-byte interleaved > bitplanes (iplan2p*), since I don't have the hardware, and am not 100% sure > how they work. But reviving 2.5.x on Atari will be even harder... Me neither. But there is a way to find out. A trick I used to figure out the hga framebuffer lay out. Build just the fbdev layer without fbcon. Then do a write to /dev/fbX to see what happens. The way I have fbdev now is when you open /dev/fb0 the hardware mode is set. When you close the /dev/fb the hardware goes back to text mode. I did it this way so you could insmod the driver and NOT change the hardware state. Also fb_open is the function register_framebuffer needs just before take_over_console happens. The other benifiet is if X dies that uses /dev/fb to set it modes then the file will be closed automatically and teh hardware state will be set to a sane state. This is for the case of vgacon with fbdev. WHat about from fbco? Well that is easy since fb_open passes a falg to let us knwo if it is from userland for fbcon. P.S It appears fbcon is totally broken in BK. I'm using the above trick to test the code. Tonight I'm going to work on making fbcon completely modular. Yeah!!!! |
|
From: Jens A. <ax...@su...> - 2002-11-25 18:14:42
|
On Mon, Nov 25 2002, Alan Cox wrote: > On Fri, 2002-11-22 at 17:49, Josh Myer wrote: > > Hi, > > > > I've got an EPIA board, with a trident CyberBlade chipset. Does anyone > > have doco on this chipset? The random Xfree stuff available from VIA is > > less-than-enlightening (I'm not familiar with X internals). > > > > I'm basically just interested in getting FB working for NTSC output. > > The chipset docs are freely downloadable from VIA (including the 3d > info). The TV on the epia is a seperate chip. I use the vesa mode switch > to program that For the record, a friend of mine pointed me to: http://epiafb.sourceforge.net/ today. fb sort of works, the mode initialization doesn't get the mode quite right it seems, but a manual fbset works for me afterwards. -- Jens Axboe |
|
From: Sven L. <lu...@dp...> - 2002-11-25 17:54:04
|
On Mon, Nov 25, 2002 at 11:01:15AM +0100, Romain Dolbeau wrote: > Chris Wilson wrote: > > >Since I can't compile this driver on my architecture, I'm afraid I haven't > >been able to test this patch at all. > > This patch is relevant for 2.5.x only, and pm3fb can't compile > and work on 2.5.x. The FB API was changed, and FB drivers > need to be rewritten. As I never found a 2.5.x release that > would compile on my box (no x86 here), I didn't port pm3fb. > > BTW, pm3fb should not be integrated in 2.5.x, it was submitted > only to 2.4.x and somehow found its way in 2.5.x. I don't > maintain pm3fb on 2.5.x, never has, and likely never will. > > The proper fix for pm3fb in 2.5 is to delete it, at least > until someone else rewrite it or until 2.5.x can actually > compile and work on PowerPC and I can rewrite it myself. I have plans for doing a full rewrite of pm3fb for 2.5, just not really the times right now. I will do it before 2.6 (or 3.0 or whatever) is released though. I have already done some work, just not filled in the mode changes and other such. That said, it may be on the limit of my NDA, which was supposed to be for XFree86 only (altough i guess the current XFree86 code counts as available from other source though. Friendly, Sven Luther |
|
From: Kyrian <ky...@or...> - 2002-11-25 14:47:14
|
James, et al, Feel free to ignore this if it's irrelevant, stupid, whatever, but... > I have tried to look for work locallly (can't really affored to move > cross country very few years) relating to the framebuffer layer. In my > search I only found one company that seemed interested in this > developement, strangeberry (http://www.strangeberry.com). I sent them my > resume but never heard from them. As for funding I serious doubt that > would happen since it isn't server related. The reality is for proper > maintiance of any subsystem you need people hired to solely work to keep > it going. Unfortunely the framebuffer layer is one of those few ones that > doesn't have that. > Did you try all of the hardware vendors that are currently supported by the fbdev system? They have the most to gain by being able to cite their products as Linux compatible, and the most to gain from financially helping, because you (as chief fbdev developer for the kernel) can then be quoted on that by the vendors. As regards the API changes, I'd be willing to put time towards helping with the Rage 128 bits (and possibly other cards that I have knocking around), at least certainly the more trivial coding and documentation areas if not the deeply technical stuff, if the current API is documented/published somewhere? K. -- Kev Green, aka Kyrian. Email: kyrian@ore.org Web: http://kyrian.ore.org/ [ Looking for ISP contract work, CV at http://kyrian.ore.org/cv.html ] "Be excellent to each other" -- Bill & Ted. |
|
From: Hanno B. <ha...@gm...> - 2002-11-25 14:44:06
|
Hi,
I would like to test the new Kernel 2.5 because it has a lot of features I'm really waiting for.
The only problem is that I want/need a working framebuffer. In the 2.5-releases, the radeonfb doesn't compile.
Is there a patch that makes it working in current 2.5-kernels?
Can you give me a download-location?
(I don't know how to use bitkeeper, so if you point me to a bitkeeper-location, please add a description how I can get things from there)
cu,
--
Hanno Boeck - ha...@gm... /"\
\ / ASCII Ribbon Campaign
Say no to DCMA, TCPA, Palladium! X Against HTML Mail
www.stop1984.com / \
|
|
From: Al. A. <ee...@ee...> - 2002-11-25 13:56:33
|
Hello, list. I've been doing some unsuccessful Googling for programmer's documentation on the CGsix. Anyone has any URLs handy? Thanks. -- Al. Andreou <ee4299 at ee.teiath.gr> http://nemesis.ee.teiath.gr/~ee4299/ |
|
From: Geert U. <ge...@li...> - 2002-11-25 10:41:45
|
On Sat, 23 Nov 2002, Jochen Roth wrote: > - Who is the current maintainer for the S3triofb? Maybe I wasn't > looking in the right places, but I didn't figure it out. I emailed > Peter de Schrijver, who is listed in the driver as author, but I > haven't heard back. > > - The current (2.4.19 for me) S3triofb has a workaround in it to > reset the PCI BAR0 register to 0xc6000000, with size 64 megs. > I a) want to figure out for what model this was necessary to add > some sort of fix, and b) this does not make sense to me as the > proper address for a 64 meg window wouldn't be 0xc6000000, but > something naturally aligned, like 0xc[48]000000. Very weird. The current S3triofb driver in the mainline kernel tree was meant for the CHRP LongTrail. It assumes Open Firmware has initialized the chip to a graphics mode. You also may want to look at cyberfb, for Amiga CyberVision/64 graphics boards, which hae a Trio as well. > - I looked briefly at http://gtf.org/garzik/kernel/files/s3fb/ -- is > this code functional? I know, I should just ask Jeff Garzik. Well, last time I tried, it didn't work on my Trio64V+ :-( > - I started out wanting to support the V2/DX in my box. Then it occured > to me that, hey, I could support all Trio64 and 32 models while I'm > at it. Next thing you know, you arrive at s3fb above. OTOH, Trios > aren't exactly cutting edge, and S3 is pretty dead these days. Maybe > the s3fb above is not in the mainline kernel for a reason? On Intel The main reason why it's not in the mainline kernel is that we have several (at least 3) S3Trio fbdevs floating around the net, and AFAIK none is known to work on all boards. But I strongly admit it would be a good thin to have generic s3fb support! > machines this hardware is probably supported by the vesa drivers, so > there it not much incentive from that perspective. What do people here > think? Most older (pre-Savage?) S3 cards don't have VESA 2.0 bioses, so vesafb doesn't work for those. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li... 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 |
|
From: Romain D. <do...@ir...> - 2002-11-25 10:02:04
|
Chris Wilson wrote: > Since I can't compile this driver on my architecture, I'm afraid I haven't > been able to test this patch at all. This patch is relevant for 2.5.x only, and pm3fb can't compile and work on 2.5.x. The FB API was changed, and FB drivers need to be rewritten. As I never found a 2.5.x release that would compile on my box (no x86 here), I didn't port pm3fb. BTW, pm3fb should not be integrated in 2.5.x, it was submitted only to 2.4.x and somehow found its way in 2.5.x. I don't maintain pm3fb on 2.5.x, never has, and likely never will. The proper fix for pm3fb in 2.5 is to delete it, at least until someone else rewrite it or until 2.5.x can actually compile and work on PowerPC and I can rewrite it myself. -- romain |
|
From: Jani M. <ja...@iv...> - 2002-11-25 06:45:26
|
Hi check out sf.net/projects/epiafb > > I've got an EPIA board, with a trident CyberBlade chipset. Does anyone > have doco on this chipset? The random Xfree stuff available from VIA is > less-than-enlightening (I'm not familiar with X internals). > > I'm basically just interested in getting FB working for NTSC output. > > Someone was working on this in the VIA forums, but i haven't noticed any > output from him recently. > > Pointers to documentation/other posts on this are greatly appreciated. > -- > /jbm, but you can call me Josh. Really, you can! > "What's a metaphor?" "For sheep to graze in" > 7958 1C1C 306A CDF8 4468 3EDE 1F93 F49D 5FA1 49C4 > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Linux-fbdev-devel mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel |
|
From: Alan C. <al...@lx...> - 2002-11-25 00:21:50
|
On Fri, 2002-11-22 at 17:49, Josh Myer wrote: > Hi, > > I've got an EPIA board, with a trident CyberBlade chipset. Does anyone > have doco on this chipset? The random Xfree stuff available from VIA is > less-than-enlightening (I'm not familiar with X internals). > > I'm basically just interested in getting FB working for NTSC output. The chipset docs are freely downloadable from VIA (including the 3d info). The TV on the epia is a seperate chip. I use the vesa mode switch to program that |
754 messages has been excluded from this view by a project administrator.
