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: James S. <jsi...@in...> - 2002-12-02 21:13:27
|
> aty128fb works for me here with: > > 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS > > Thank you! Great. I made more inprovements with my latest patch. Give it a try. > There are a few glitches, but I've been unable to pin down > anything serious as the fbdev patch's fault. I'm still playing with > things (like Antonio Daplas' patches). I'll give a more full report > later. I just intergrated a bunch of his work. The subsystem is starting to really take shape. > FWIW, the fbdev patch applies with a few minor offsets to 2.5.50 > except for the attached patch, which I extracted from bk. So if you > apply this patch in *reverse* to a clean 2.5.50 tree, the fbdev patch > should then apply okay (patch complained about a reversed hunk in > fbcon.c, but it should be harmless, I think.) I noticed. My new patch fixes that. |
|
From: James S. <jsi...@in...> - 2002-12-02 21:09:07
|
Hi! I have a new patch avaiable. It is against 2.5.50. The patch is at http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz Have fun!!!! Drivers ported are: (Give them a try) ATI Mach 64 ATI 128 VESA VGA16 HGA NIVIDA NEOMAGIC The BIG changes are: 1) The seperation of the console code out of the fbdev drivers. 2) Total modularity of the frmaebuffer console system. Yes that is right. You can build it has modules. Great for testing. The following are results of the new changes which I have tested. With my VIA laptop with my neomagic card I was able to build it with vgacon and no fbcon. Then I insmod neofb and the soft accel (cfb*.c) needed. It loading and did NOT change the video hardware state. At this point I could run fbdev apps including a X server using /dev/fb solely. On opening /dev/fb0 the graphics hardware state changed. In theory I could exit X and get vgacon back. In order to do this I have to reset the hardware back to vga text mode in the fb_release function. It can be done but I haven't done it yet. With the second experiment I was able to insmod the fonts and fbcon.o. Then it switched from vgacon to fbcon. In theory I could again call the release function and reset the hardware back to a text mode state. All that is needed is the hardware specific code to do this. Things to be done: 1) A few bugs in fbcon to hammer out. 2) Fbcon to support changing resolution via the console layer. 3) Move the logo code out of fbcon.c to fbmem.c. With pure fbdev you need something to let you know things worked. 4) Software rotation. The diffstat is: CREDITS | 10 Documentation/DocBook/kernel-api.tmpl | 4 Documentation/fb/README-sstfb.txt | 173 Documentation/fb/internals.txt | 5 Documentation/fb/sstfb.txt | 174 MAINTAINERS | 7 arch/alpha/Kconfig | 31 arch/arm/Kconfig | 21 arch/i386/Kconfig | 55 arch/i386/vmlinux.lds.s | 114 arch/ia64/Kconfig | 25 arch/m68k/Kconfig | 7 arch/m68knommu/Kconfig | 35 arch/mips/Kconfig | 62 arch/mips64/Kconfig | 23 arch/parisc/Kconfig | 30 arch/ppc/Kconfig | 22 arch/ppc64/Kconfig | 7 arch/sh/Kconfig | 55 arch/sparc/Kconfig | 16 arch/sparc64/Kconfig | 11 arch/v850/Kconfig | 35 arch/x86_64/Kconfig | 55 drivers/Makefile | 3 drivers/char/Makefile | 2 drivers/char/consolemap.c | 5 drivers/char/keyboard.c | 1 drivers/char/mem.c | 12 drivers/char/selection.c | 1 drivers/char/toshiba.c | 2 drivers/char/tty_io.c | 7 drivers/char/vc_screen.c | 1 drivers/char/vt.c | 200 - drivers/char/vt_ioctl.c | 58 drivers/video/68328fb.c | 967 +---- drivers/video/Kconfig | 411 -- drivers/video/Makefile | 54 drivers/video/S3triofb.c | 2 drivers/video/amifb.c | 2 drivers/video/anakinfb.c | 62 drivers/video/atafb.c | 2 drivers/video/aty/atyfb.h | 18 drivers/video/aty/atyfb_base.c | 99 drivers/video/aty/mach64_ct.c | 2 drivers/video/aty/mach64_cursor.c | 157 drivers/video/aty/mach64_gx.c | 2 drivers/video/aty128fb.c | 3238 +++++++---------- drivers/video/cfbcopyarea.c | 511 +- drivers/video/cfbfillrect.c | 536 ++ drivers/video/cfbimgblt.c | 360 + drivers/video/chipsfb.c | 2 drivers/video/clps711xfb.c | 16 drivers/video/console/Kconfig | 221 + drivers/video/console/Makefile | 61 drivers/video/console/dummycon.c | 73 drivers/video/console/fbcon-sti.c | 289 + drivers/video/console/fbcon.c | 2725 ++++++++++++++ drivers/video/console/fbcon.h | 142 drivers/video/console/font.h | 53 drivers/video/console/font_6x11.c | 3351 +++++++++++++++++ drivers/video/console/font_8x16.c | 4631 ++++++++++++++++++++++++ drivers/video/console/font_8x8.c | 2583 +++++++++++++ drivers/video/console/font_acorn_8x8.c | 277 + drivers/video/console/font_mini_4x6.c | 2158 +++++++++++ drivers/video/console/font_pearl_8x8.c | 2587 +++++++++++++ drivers/video/console/font_sun12x22.c | 6220 +++++++++++++++++++++++++++++++++ drivers/video/console/font_sun8x16.c | 275 + drivers/video/console/fonts.c | 142 drivers/video/console/mdacon.c | 631 +++ drivers/video/console/newport_con.c | 745 +++ drivers/video/console/prom.uni | 11 drivers/video/console/promcon.c | 605 +++ drivers/video/console/sti.h | 289 + drivers/video/console/sticon.c | 214 + drivers/video/console/sticore.c | 601 +++ drivers/video/console/vgacon.c | 1066 +++++ drivers/video/controlfb.c | 499 -- drivers/video/cyberfb.c | 2 drivers/video/dnfb.c | 18 drivers/video/dummycon.c | 74 drivers/video/epson1355fb.c | 2 drivers/video/fbcmap.c | 92 drivers/video/fbcon-accel.c | 188 drivers/video/fbcon-accel.h | 34 drivers/video/fbcon-afb.c | 448 -- drivers/video/fbcon-cfb16.c | 319 - drivers/video/fbcon-cfb2.c | 225 - drivers/video/fbcon-cfb24.c | 333 - drivers/video/fbcon-cfb32.c | 305 - drivers/video/fbcon-cfb4.c | 229 - drivers/video/fbcon-cfb8.c | 294 - drivers/video/fbcon-hga.c | 253 - drivers/video/fbcon-ilbm.c | 296 - drivers/video/fbcon-iplan2p2.c | 476 -- drivers/video/fbcon-iplan2p4.c | 497 -- drivers/video/fbcon-iplan2p8.c | 534 -- drivers/video/fbcon-mfb.c | 217 - drivers/video/fbcon-sti.c | 337 - drivers/video/fbcon-vga-planes.c | 387 -- drivers/video/fbcon.c | 2509 ------------- drivers/video/fbgen.c | 286 - drivers/video/fbmem.c | 233 - drivers/video/fm2fb.c | 17 drivers/video/font_6x11.c | 3351 ----------------- drivers/video/font_8x16.c | 4631 ------------------------ drivers/video/font_8x8.c | 2583 ------------- drivers/video/font_acorn_8x8.c | 277 - drivers/video/font_mini_4x6.c | 2158 ----------- drivers/video/font_pearl_8x8.c | 2587 ------------- drivers/video/font_sun12x22.c | 6220 --------------------------------- drivers/video/font_sun8x16.c | 275 - drivers/video/fonts.c | 135 drivers/video/g364fb.c | 74 drivers/video/hgafb.c | 424 -- drivers/video/hitfb.c | 17 drivers/video/hpfb.c | 16 drivers/video/igafb.c | 2 drivers/video/imsttfb.c | 41 drivers/video/macfb.c | 22 drivers/video/macmodes.c | 3 drivers/video/macmodes.h | 70 drivers/video/matrox/i2c-matroxfb.c | 2 drivers/video/matrox/matroxfb_base.c | 4 drivers/video/matrox/matroxfb_crtc2.c | 4 drivers/video/maxinefb.c | 48 drivers/video/mdacon.c | 632 --- drivers/video/modedb.c | 7 drivers/video/neofb.c | 389 +- drivers/video/newport_con.c | 746 --- drivers/video/offb.c | 23 drivers/video/platinumfb.c | 451 -- drivers/video/pm2fb.c | 2 drivers/video/pm3fb.c | 2 drivers/video/pmag-ba-fb.c | 59 drivers/video/pmagb-b-fb.c | 53 drivers/video/prom.uni | 11 drivers/video/promcon.c | 606 --- drivers/video/pvr2fb.c | 4 drivers/video/q40fb.c | 16 drivers/video/radeonfb.c | 3374 ++++++++++------- drivers/video/retz3fb.c | 2 drivers/video/riva/Makefile | 2 drivers/video/riva/accel.c | 427 -- drivers/video/riva/fbdev.c | 2099 ++++------- drivers/video/riva/riva_hw.h | 1 drivers/video/riva/rivafb.h | 48 drivers/video/sa1100fb.c | 2 drivers/video/sbusfb.c | 2 drivers/video/sgivwfb.c | 62 drivers/video/sis/Makefile | 2 drivers/video/sis/sis_accel.c | 495 ++ drivers/video/sis/sis_main.c | 2 drivers/video/skeletonfb.c | 28 drivers/video/softcursor.c | 62 drivers/video/sstfb.c | 2 drivers/video/sti-bmode.h | 287 - drivers/video/sti.h | 289 - drivers/video/sticon-bmode.c | 895 ---- drivers/video/sticon.c | 215 - drivers/video/sticore.c | 601 --- drivers/video/sticore.h | 407 ++ drivers/video/stifb.c | 1403 ++++++- drivers/video/sun3fb.c | 2 drivers/video/tdfxfb.c | 531 +- drivers/video/tgafb.c | 2 drivers/video/tridentfb.c | 2 drivers/video/tx3912fb.c | 19 drivers/video/valkyriefb.c | 27 drivers/video/vesafb.c | 24 drivers/video/vfb.c | 38 drivers/video/vga16fb.c | 1368 +++++-- drivers/video/vgacon.c | 1055 ----- drivers/video/virgefb.c | 2 include/linux/console.h | 1 include/linux/console_struct.h | 1 include/linux/fb.h | 207 - include/linux/radeon.h | 766 ++++ include/linux/radeonfb.h | 15 include/linux/sisfb.h | 58 include/linux/vt_kern.h | 8 include/video/fbcon-afb.h | 32 include/video/fbcon-cfb16.h | 34 include/video/fbcon-cfb2.h | 32 include/video/fbcon-cfb24.h | 34 include/video/fbcon-cfb32.h | 34 include/video/fbcon-cfb4.h | 32 include/video/fbcon-cfb8.h | 34 include/video/fbcon-hga.h | 32 include/video/fbcon-ilbm.h | 32 include/video/fbcon-iplan2p2.h | 32 include/video/fbcon-iplan2p4.h | 32 include/video/fbcon-iplan2p8.h | 32 include/video/fbcon-mac.h | 32 include/video/fbcon-mfb.h | 32 include/video/fbcon-vga-planes.h | 37 include/video/fbcon-vga.h | 32 include/video/fbcon.h | 795 ---- include/video/font.h | 53 include/video/macmodes.h | 70 include/video/neomagic.h | 1 kernel/printk.c | 1 201 files changed, 41728 insertions(+), 47259 deletions(-) |
|
From: James S. <jsi...@in...> - 2002-12-02 20:33:53
|
> 1. Added full hardware acceleration (should be 3 - 4x faster thant 2.4 > version with the putcs optimization.) > 2. Added hardware cursor support > 3. Fixed wrong color at depths > 8bpp, at least for the Riva128. Applied but not tested. I can tets it out tonight when I get home. |
|
From: James S. <jsi...@in...> - 2002-12-02 20:32:59
|
> Attached is a patch against 2.5.49 + James Simmons' latest fbdev.diff.
>
> Added support for logo drawing.
> Fixed vga16fb_imageblit() limitation of 8-pixel wide bitmap blitting
> only.
Applied and tested :-=) The only weird thing is it drew the logo twice
when I don't have a SMP laptop. It works other than that.
P.S
Things I like to get done for the vga16fb driver.
1) Its own read and write functions to fake a linear framebuffer.
2) The ability to go back to vga text mode on close of /dev/fb.
Yes fbdev/fbcon supports that now.
|
|
From: James S. <jsi...@in...> - 2002-12-02 20:23:48
|
> The following is against 2.5 current and fixes an timer > warning I'm getting during boot. I noticed :-/ I have the fix in BK. I plan to soon send Linus my changes now that fbdev is maturing. |
|
From: <rw...@ea...> - 2002-12-01 22:17:58
|
>> Call Trace: >> [<c011c340>] check_timer_failed+0x40/0x50 >> [<c01c9050>] cursor_timer_handler+0x0/0x30 > Yes, the timer initialization was reverted in 2.5.50. Please apply the patch > Mathijs Mohlmann send to this list. Yes, Mathijs' patch eliminates the call trace at boot time. Thanks! -- Randy Hron http://home.earthlink.net/~rwhron/kernel/bigbox.html |
|
From: Jon S. <jon...@ya...> - 2002-12-01 22:03:33
|
This patch fixes the syntax in fbtest so that gcc 3.2 is happy. I also adjusted the libs for the current version of libnetpbm. I went searching for libnetpnm which doesn't seem to exist standalone any more. It is part of libnetpbm now. ===== Jon Smirl jon...@ya... __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com |
|
From: Nico S. <sch...@wd...> - 2002-12-01 21:36:49
|
Hello Guys! I tried to get my notebook running with a framebuffer device,but after hours trying around I got only vesa-fb running. Which is in fact nice, but _slow_. I tried to use aty128fb and atyfb with Linux 2.4.19 and 2.5.47-50. I never achieved something 'displayable'. Can you tell me,=20 a) is my chipset compatible with the atyfb/aty128fb driver ? b) what todo exactly to get it working ? (i know howto compile kernel, patch around code,... what I need are informations, whether append=3D"video=3Daty128fb:accel,<640x480@8bpp>" or=20 append=3D"video=3Datyfb:<800x600-16bpp>" are correct, whether to pass vga=3D options to the kernel is senseful and so on...) If possible I would like to use the 1024x768x24 framebuffer device, perhaps loadable via module. My chipset: 01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage P/M Mobilit= y AGP 2x (rev 64) 01:00.0 Class 0300: 1002:4c4d (rev 64) Please tell me whether I should sent more informations or if you need to see .config and so on. Sincerly, Nico --=20 Please send your messages pgp-signed and/or pgp-encrypted (don't encrypt ma= ils 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) |
|
From: Geert U. <ge...@li...> - 2002-12-01 20:36:55
|
On Thu, 28 Nov 2002 rw...@ea... wrote:
> I saw the call trace below during 2.5.50 boot, but not on:
> 2.5.44-mm5
> 2.5.46-mm1
> 2.5.47-mm1
> 2.5.47-mm2
> 2.5.48-mm1
> 2.5.49
> 2.5.49-mm1
>
> Invalid vesa mode 0x0000
> matroxfb: Matrox G400 (AGP) detected
> matroxfb: MTRR's turned on
> matroxfb: 1920x1440x8bpp (virtual: 1920x8736)
> matroxfb: framebuffer at 0xD4000000, mapped to 0xf8805000, size 33554432
> Uninitialised timer!
> This is just a warning. Your computer is OK
> function=0xc01c9050, data=0x0
> Call Trace:
> [<c011c340>] check_timer_failed+0x40/0x50
> [<c01c9050>] cursor_timer_handler+0x0/0x30
Yes, the timer initialization was reverted in 2.5.50. Please apply the patch
Mathijs Mohlmann send to this list.
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: Ramprasad <ram...@nc...> - 2002-11-30 13:35:45
|
Hi All, I am working on assabet board with 320x240 mono LCD panel , kernel 2.4.18 i want to display full screen logo while boot up. I have set the pixel clock value = 70000 , and bpp is 4 bit. I am not getting the logo. i get 4 small , compressed linux logo . Then i changed the pixclock to 171521 and bpp to 8. now iam getting the full logo but there is lot of wavey lines....... I am using the patchs given by arnor.net Can anybody guide me ... Thanks in advance, Ramprasad |
|
From: <rw...@ea...> - 2002-11-28 23:36:19
|
I saw the call trace below during 2.5.50 boot, but not on: 2.5.44-mm5 2.5.46-mm1 2.5.47-mm1 2.5.47-mm2 2.5.48-mm1 2.5.49 2.5.49-mm1 Invalid vesa mode 0x0000 matroxfb: Matrox G400 (AGP) detected matroxfb: MTRR's turned on matroxfb: 1920x1440x8bpp (virtual: 1920x8736) matroxfb: framebuffer at 0xD4000000, mapped to 0xf8805000, size 33554432 Uninitialised timer! This is just a warning. Your computer is OK function=0xc01c9050, data=0x0 Call Trace: [<c011c340>] check_timer_failed+0x40/0x50 [<c01c9050>] cursor_timer_handler+0x0/0x30 [<c011c37e>] add_timer+0x2e/0xf0 [<c01c9383>] fbcon_startup+0x43/0x50 [<c01a0267>] take_over_console+0x17/0x190 [<c01c87ec>] register_framebuffer+0x11c/0x150 [<c01cf441>] initMatrox2+0x8d1/0x9a0 [<c01cf99d>] matroxfb_probe+0x24d/0x280 [<c01872b1>] pci_device_probe+0x41/0x60 [<c018dce7>] bus_match+0x37/0x70 [<c018ddd3>] driver_attach+0x43/0x70 [<c018e092>] bus_add_driver+0x92/0xc0 [<c0117425>] printk+0x105/0x120 [<c018e444>] driver_register+0x34/0x40 [<c01873c2>] pci_register_driver+0x42/0x60 [<c0105030>] init+0x0/0x140 [<c010504f>] init+0x1f/0x140 [<c0105030>] init+0x0/0x140 [<c0106e5d>] kernel_thread_helper+0x5/0x18 Console: switching to colour frame buffer device 240x90 fb0: MATROX VGA frame buffer device This is what's in .config: CONFIG_FB=y CONFIG_FB_MATROX=y CONFIG_FB_MATROX_G450=y CONFIG_FB_MATROX_G100=y CONFIG_FBCON_ADVANCED=y CONFIG_FBCON_CFB8=y CONFIG_FBCON_ACCEL=y lilo append has this: video=matrox:vesa:depth:8,fh:115,fv:92,xres:1920,yres:1440,left:392,right:124 So far, everything appears to be working okay. -- Randy Hron http://home.earthlink.net/~rwhron/kernel/bigbox.html |
|
From: Szymanski, Frank-P. <F.S...@dm...> - 2002-11-28 14:33:41
|
Hi Geert, > You don't need X to run fbtest. Even better, do _not_ run it > under X! All you need is a kernel with atafb. I've got such a kernel. :-) > > Just tell me where I can find the above mentioned ramdisk. > It's not yet available. Don't expect it before next weekend, though. My installed Linux setup is approx. 2 years old, so as you can see I am a very patient person. ;-) > To compile your own fbtest, all you need is a working C > compiler, netpbm, and cvs to get the sources. As X11 doesn't work any longer on my machine :-( and the 2.0.36 kernels are quite old now I don't have a current working setup with the above mentioned programs but I would like to help us much as possible (e.g. testing the ramdisk). Regards, Frank |
|
From: Geert U. <ge...@li...> - 2002-11-28 12:34:28
|
On Thu, 28 Nov 2002, Szymanski, Frank-Peter wrote: > >Anyone who cares to give it a try? Just check out CVS module `fbtest' from > >http://sourceforge.net/cvs/?group_id=908, type `make' and run `fbtest' for > all > >available color depths (use fbset first), and tell me whether it works. > > >If no one is left with an Atari with Linux/m68k installed, I can create a > >ramdisk containing fbset and fbtest, so you just need ataboot and a kernel > to > >test it. > > Due to the fact that since kernel 2.2.x X11 doesn't work any longer on > ATARIs I don't have a working Linux/m68k configuration ATM but I have both a > 2.0.3x/2.2.x kernel and ataboot to test it if you like. You don't need X to run fbtest. Even better, do _not_ run it under X! All you need is a kernel with atafb. > Just tell me where I can find the above mentioned ramdisk. It's not yet available. Don't expect it before next weekend, though. To compile your own fbtest, all you need is a working C compiler, netpbm, and cvs to get the sources. 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: Szymanski, Frank-P. <F.S...@dm...> - 2002-11-28 12:25:03
|
Hi Geert, >Anyone who cares to give it a try? Just check out CVS module `fbtest' from >http://sourceforge.net/cvs/?group_id=908, type `make' and run `fbtest' for all >available color depths (use fbset first), and tell me whether it works. >If no one is left with an Atari with Linux/m68k installed, I can create a >ramdisk containing fbset and fbtest, so you just need ataboot and a kernel to >test it. Due to the fact that since kernel 2.2.x X11 doesn't work any longer on ATARIs I don't have a working Linux/m68k configuration ATM but I have both a 2.0.3x/2.2.x kernel and ataboot to test it if you like. Just tell me where I can find the above mentioned ramdisk. Regards, Frank |
|
From: Joseph F. <jh...@ri...> - 2002-11-28 08:32:51
|
On Wed, Nov 27, 2002 at 11:18:22PM +0000, James Simmons wrote:
>=20
> > No. The machine froze solid. No oops, no sysrq.
> > The reset button worked.
>=20
> VESA fbdev did this to me. I have no trouble with neofb. Strange???
> I will track it down tonight.
aty128fb works for me here with:
01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP=
4x TMDS
Thank you!
There are a few glitches, but I've been unable to pin down
anything serious as the fbdev patch's fault. I'm still playing with
things (like Antonio Daplas' patches). I'll give a more full report
later.
FWIW, the fbdev patch applies with a few minor offsets to 2.5.50
except for the attached patch, which I extracted from bk. So if you
apply this patch in *reverse* to a clean 2.5.50 tree, the fbdev patch
should then apply okay (patch complained about a reversed hunk in
fbcon.c, but it should be harmless, I think.)
=20
--=20
Joseph Fannin
jh...@ri...
"Anyone who quotes me in their sig is an idiot." -- Rusty Russell.
|
|
From: Antonino D. <ad...@po...> - 2002-11-28 04:33:53
|
Hi, Attached is a patch against 2.5.49 + James Simmons' latest fbdev.diff. This fixes fbcon oopsing at load time which is due to the fb_cursor's palette index entries being improperly updated. A new kind of 'emacs glitch' appeared, though. This can be described as a block of text that is incompletely copied, ie when "tabbing" a line of text. This is present with all hardware I tested, soft accel and hardware accel, which indicates a problem in the higher layers (probably fbcon). vgacon works okay. Other changes: 1. optimization of fbcon_accel_putcs() 2. enabling logo displays at all packed pixel formats (as long as fb_imageblit is supported) 3. Various fbcon_accel_cursor() fixes which would have resulted in wrong cursor colors or an invisible cursor. Tony |
|
From: Antonino D. <ad...@po...> - 2002-11-28 04:33:19
|
Attached is a patch against 2.5.49 + James Simmons' latest fbdev.diff. Added support for logo drawing. Fixed vga16fb_imageblit() limitation of 8-pixel wide bitmap blitting only. Tony |
|
From: Antonino D. <ad...@po...> - 2002-11-28 04:32:46
|
Attached is a patch against 2.5.49 + James Simmons' latest fbdev.diff. 1. Added full hardware acceleration (should be 3 - 4x faster thant 2.4 version with the putcs optimization.) 2. Added hardware cursor support 3. Fixed wrong color at depths > 8bpp, at least for the Riva128. Tony |
|
From: James S. <jsi...@in...> - 2002-11-27 23:19:29
|
> No. The machine froze solid. No oops, no sysrq. > The reset button worked. VESA fbdev did this to me. I have no trouble with neofb. Strange??? I will track it down tonight. > > Hm. Are you using a PPC or ix86 box? I will test this tonight. > i386. Specifically, a pentium II, compiled for pentium II. Hm. I have that same card and a similar machine. > Perhaps. It didn't look like it ended at the bottom of the > screen, but then it might have been panning at the wrong moment. I have a MDA monitor and card. So I can setup mdacon and turn on debugging in fbcon and trace threw it. > > > 2.5.49 without this patch works. I use devfs & preempt, > > > the machine is UP and I use gcc-2.95.4 for compiling. > > Helge Hafting > |
|
From: Geert U. <ge...@li...> - 2002-11-27 23:04:50
|
On 25 Nov 2002, Johan Bolmsjo wrote: > 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. Thanks! This is exactly the kind of information I needed! I added simple unoptimized support for Atari interleaved bitplanes to fbtest. When I know I got the basics right, I can start writing optimized drawing routines. Anyone who cares to give it a try? Just check out CVS module `fbtest' from http://sourceforge.net/cvs/?group_id=908, type `make' and run `fbtest' for all available color depths (use fbset first), and tell me whether it works. If no one is left with an Atari with Linux/m68k installed, I can create a ramdisk containing fbset and fbtest, so you just need ataboot and a kernel to test it. Thanks! 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: Helge H. <hel...@ai...> - 2002-11-27 18:08:14
|
James Simmons wrote: > > > I tried this patch, but it crashed during boot. > > Any oops info? No. The machine froze solid. No oops, no sysrq. The reset button worked. > > > I have a > > 01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP > > 1X/2X (rev 5c) > > > > and use this in lilo.conf: > > image=/boot/2.5.49fb > > label=2.5.49fb > > append="video=atyfb:1280x1024-16@85" > > Hm. Are you using a PPC or ix86 box? I will test this tonight. i386. Specifically, a pentium II, compiled for pentium II. > > This got me a 160x64 framebuffer with yellow text on > > blue background. Nice, but only got about 10 lines before > > the kernel hung. The disk light got stuck on and there were > > no response to things like sysrq. > > The few lines displayed was about the fb, drm, and finally > > the 3com network adapter. Then nothing more. > > Sounds like panning flipped put. > Perhaps. It didn't look like it ended at the bottom of the screen, but then it might have been panning at the wrong moment. > > 2.5.49 without this patch works. I use devfs & preempt, > > the machine is UP and I use gcc-2.95.4 for compiling. Helge Hafting |
|
From: James S. <jsi...@in...> - 2002-11-27 17:50:36
|
> I tried this patch, but it crashed during boot. Any oops info? > I have a > 01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP > 1X/2X (rev 5c) > > and use this in lilo.conf: > image=/boot/2.5.49fb > label=2.5.49fb > append="video=atyfb:1280x1024-16@85" Hm. Are you using a PPC or ix86 box? I will test this tonight. > This got me a 160x64 framebuffer with yellow text on > blue background. Nice, but only got about 10 lines before > the kernel hung. The disk light got stuck on and there were > no response to things like sysrq. > The few lines displayed was about the fb, drm, and finally > the 3com network adapter. Then nothing more. Sounds like panning flipped put. > 2.5.49 without this patch works. I use devfs & preempt, > the machine is UP and I use gcc-2.95.4 for compiling. |
|
From: James S. <jsi...@in...> - 2002-11-27 17:44:28
|
> > 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. No problem. Thank you for your support. |
|
From: Helge H. <hel...@ai...> - 2002-11-27 11:04:33
|
James Simmons wrote: > 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 tried this patch, but it crashed during boot. I have a 01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP 1X/2X (rev 5c) and use this in lilo.conf: image=/boot/2.5.49fb label=2.5.49fb append="video=atyfb:1280x1024-16@85" This got me a 160x64 framebuffer with yellow text on blue background. Nice, but only got about 10 lines before the kernel hung. The disk light got stuck on and there were no response to things like sysrq. The few lines displayed was about the fb, drm, and finally the 3com network adapter. Then nothing more. 2.5.49 without this patch works. I use devfs & preempt, the machine is UP and I use gcc-2.95.4 for compiling. Helge Hafting |
|
From: <ee...@ee...> - 2002-11-27 07:55:39
|
> > 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. Yes, that fb. If you find anything, please send it in or upload it somewhere. Like on infradead :-))))))) . That's a nice one. -- Al. Andreou <ee...@ee...> | http://nemesis.ee.teiath.gr/~ee4299/ |
754 messages has been excluded from this view by a project administrator.
