You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(210) |
Jun
(169) |
Jul
(167) |
Aug
(128) |
Sep
(218) |
Oct
(120) |
Nov
(86) |
Dec
(71) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(91) |
Feb
(179) |
Mar
(52) |
Apr
(56) |
May
(183) |
Jun
(62) |
Jul
(63) |
Aug
(49) |
Sep
(36) |
Oct
(35) |
Nov
(72) |
Dec
(30) |
2002 |
Jan
(53) |
Feb
(61) |
Mar
(56) |
Apr
(13) |
May
(1) |
Jun
(7) |
Jul
(80) |
Aug
(73) |
Sep
(30) |
Oct
(29) |
Nov
(8) |
Dec
(40) |
2003 |
Jan
(10) |
Feb
(2) |
Mar
(4) |
Apr
(9) |
May
(3) |
Jun
(19) |
Jul
(64) |
Aug
(53) |
Sep
(28) |
Oct
(7) |
Nov
(3) |
Dec
(21) |
2004 |
Jan
(11) |
Feb
(30) |
Mar
(18) |
Apr
(1) |
May
(13) |
Jun
(18) |
Jul
(13) |
Aug
|
Sep
(9) |
Oct
(5) |
Nov
|
Dec
|
2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(10) |
Aug
(21) |
Sep
(7) |
Oct
(10) |
Nov
(6) |
Dec
|
2006 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
(6) |
Oct
(10) |
Nov
(8) |
Dec
(3) |
2007 |
Jan
(3) |
Feb
(6) |
Mar
(1) |
Apr
(6) |
May
(10) |
Jun
(7) |
Jul
(13) |
Aug
(8) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
From: Roman Z. <zi...@fh...> - 2000-08-03 16:34:37
|
Hi, > Thanks for the fix Geert, I've committed it, as well as a fix for a few > unresolved symbols for modules. Who needs vmalloc exported? It's an inline function in <linux/vmalloc.h>. Anyway, tomorrow I hopefully can update to test5 and I have a first version of affstools. :) After that I can do some more tests with affs. bye, Roman |
From: Michel <dae...@st...> - 2000-08-03 15:45:45
|
Geert Uytterhoeven wrote: > Ah, stupid typo. The CV64 has 4 MB RAM, not 64... I also missed the release > in case of an error. Does the patch below help? > > Just wondering why no one ever noticed this ;-) I guess because noone ever tested it :( Thanks for the fix Geert, I've committed it, as well as a fix for a few unresolved symbols for modules. I'm now uploading a test kernel for the masses... Michel -- There's no place like ~ ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
From: Glenn H. <gh...@c2...> - 2000-08-03 14:22:21
|
Hello, On 03-Aug-2000, Geert wrote: > On Thu, 3 Aug 2000, Glenn Hisdal wrote: >>> On Wed, 2 Aug 2000, Glenn Hisdal wrote: >>>> On 02-Aug-2000, you wrote: >> >>>> I still can't get the cybervision64 driver to work in 2.4 though (It >> >>>> compiles fine, but I can't use it). >> >>>> The kernel just uses amifb:vga even if i tell it to use cyberfb... >> Please #define CYBERFBDEBUG in drivers/video/cyberfb.c and tell us more. >> done. >> Here's the dmesg output : > [...] >> cyberfb_init: ENTER > And nothing more. So it fails in the resource management code. > Ah, stupid typo. The CV64 has 4 MB RAM, not 64... I also missed the > release in case of an error. Does the patch below help? Yepp ! It works now. Thanks :-) - glenn |
From: Geert U. <ge...@li...> - 2000-08-03 13:06:17
|
On Thu, 3 Aug 2000, Glenn Hisdal wrote: > > On Wed, 2 Aug 2000, Glenn Hisdal wrote: > >> On 02-Aug-2000, you wrote: > >>>> I still can't get the cybervision64 driver to work in 2.4 though (It > >>>> compiles fine, but I can't use it). > >>>> The kernel just uses amifb:vga even if i tell it to use cyberfb... > >> > >>> Looking at drivers/video/fbmem.c, you should try video=cyber:... > >> > >> Yes, that's what I use... (video=cyber:800x600-8) > >> won't work. Guess I'll have to stick with 2.2.10 a litte longer. > > > Please #define CYBERFBDEBUG in drivers/video/cyberfb.c and tell us more. > > done. > Here's the dmesg output : [...] > cyberfb_init: ENTER And nothing more. So it fails in the resource management code. Ah, stupid typo. The CV64 has 4 MB RAM, not 64... I also missed the release in case of an error. Does the patch below help? Just wondering why no one ever noticed this ;-) --- linux-2.4.0-test6-pre1/drivers/video/cyberfb.c.orig Fri Jul 28 21:19:18 2000 +++ linux-2.4.0-test6-pre1/drivers/video/cyberfb.c Thu Aug 3 14:24:20 2000 @@ -1066,7 +1066,7 @@ CyberRegs_phys = CyberMem_phys + 0x00c00000; if (!request_mem_region(CyberRegs_phys, 0x10000, "S3 Trio64")) continue; - if (!request_mem_region(CyberMem_phys, 0x4000000, "RAM")) { + if (!request_mem_region(CyberMem_phys, 0x400000, "RAM")) { release_mem_region(CyberRegs_phys, 0x10000); continue; } @@ -1110,7 +1110,8 @@ if (register_framebuffer(&fb_info) < 0) { DPRINTK("EXIT - register_framebuffer failed\n"); - release_mem_region(board_addr, board_size); + release_mem_region(CyberMem_phys, 0x400000); + release_mem_region(CyberRegs_phys, 0x10000); return -EINVAL; } 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: Geert U. <ge...@li...> - 2000-08-03 13:06:08
|
On Wed, 2 Aug 2000 fh...@at... wrote: > In <Pine.LNX.4.10.10008021413270.427-100000@cassiopeia.home>, on 08/02/00 > at 02:14 PM, Geert Uytterhoeven <ge...@li...> said: > > >And it does show up in /proc/bus/zorro (lszorro) with the same ID? > >/proc/bus/zorro/devices contains a line with 13890600 in the 2nd column? > > This is the output from cat /proc/bus/zorro etc. > > I can't see any discrepancies. Can you? > > amiga1:/usr/src/linux/drivers/char# cat /proc/bus/zorro/devices > 00 13890600 00e90000 00010000 c1 Hmm... Then I don't see what's wrong... Can you add debug code to zorro_find()? Oh, I just notice you're using 2.2.x and not 2.[34].x? Are you working on a modular driver? If yes, you perhaps once did find the board and called zorro_config_board() without a matching call to zorro_unconfig_board()? If that happens, the board is still marked busy and zorro_find() won't find it anymore. You can In 2.[34].x, you should use zorro_find_device() and {request,release}_mem_region() to mark the board busy. Then it'll also show up in /proc/iomem. BTW, I'm interested in your /proc/iomem anyway since I never saw it for a box with more than 1 Zorro board (I have the Ariadne only). 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: <fh...@at...> - 2000-08-03 01:00:27
|
In <Pine.LNX.4.10.10008021413270.427-100000@cassiopeia.home>, on 08/02/00 at 02:14 PM, Geert Uytterhoeven <ge...@li...> said: >And it does show up in /proc/bus/zorro (lszorro) with the same ID? >/proc/bus/zorro/devices contains a line with 13890600 in the 2nd column? Geert, This is the output from cat /proc/bus/zorro etc. I can't see any discrepancies. Can you? amiga1:/usr/src/linux/drivers/char# cat /proc/bus/zorro/devices 00 13890600 00e90000 00010000 c1 01 0877c900 00ea0000 00010000 c1 02 21404300 40000000 10000000 84 03 38a50200 00eb0000 00010000 c1 04 21406400 00f01060 00020000 d2 amiga1:/usr/src/linux/drivers/char# cat /proc/bus/zorro/devices >/usr/src/zorro_devices.txt amiga1:/usr/src/linux/drivers/char# grep VMC /usr/src/linux/include/linux//zorro.h #define ZORRO_MANUF_VMC 0x1389 #define ZORRO_PROD_VMC_ISDN_BLASTER_Z2 ZORRO_ID(VMC, 0x01, 0) #define ZORRO_PROD_VMC_HYPERCOM_4 ZORRO_ID(VMC, 0x02, 0) #define ZORRO_PROD_VMC_HYPERCOM_4_PLUS ZORRO_ID(VMC, 0x06, 0) amiga1:/usr/src/linux/drivers/char# grep PETSOFF /usr/src/linux/include/linux//zorro.h #define ZORRO_MANUF_PETSOFF_LP 0x38A5 #define ZORRO_PROD_PETSOFF_LP_DELFINA ZORRO_ID(PETSOFF_LP, 0x00, 0) #define ZORRO_PROD_PETSOFF_LP_DELFINA_LITE ZORRO_ID(PETSOFF_LP, 0x01, 0) #define ZORRO_PROD_PETSOFF_LP_DELFINA_PLUS ZORRO_ID(PETSOFF_LP, 0x02, 0) Fred ----------------------------------------------------- -- End of forwarded message ----------------------------------------------------- -- ----------------------------------------------------------- fh...@at... ----------------------------------------------------------- |
From: Glenn H. <gh...@c2...> - 2000-08-02 22:28:51
|
Hello Geert On 02-Aug-2000, you wrote: > On Wed, 2 Aug 2000, Glenn Hisdal wrote: >> On 02-Aug-2000, you wrote: >>>> I still can't get the cybervision64 driver to work in 2.4 though (It >>>> compiles fine, but I can't use it). >>>> The kernel just uses amifb:vga even if i tell it to use cyberfb... >> >>> Looking at drivers/video/fbmem.c, you should try video=cyber:... >> >> Yes, that's what I use... (video=cyber:800x600-8) >> won't work. Guess I'll have to stick with 2.2.10 a litte longer. > Please #define CYBERFBDEBUG in drivers/video/cyberfb.c and tell us more. done. Here's the dmesg output : parse_bootinfo: unknown tag 0x8008 ignored parse_bootinfo: unknown tag 0x8009 ignored Total memory = 64MB; using 256kB for hash table (at c0200000) Linux version 2.4.0-test4 (ro...@gu...d) (gcc version 2.95.2 19991024 (release/franzo)) #1 Wed Aug 2 23:29:25 GMT 2000 Amiga hardware found: [A4000] VIDEO BLITTER AUDIO FLOPPY A4000_IDE KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA LISA ALICE_PAL ZORRO3 On node 0 totalpages: 16384 zone(0): 16384 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/hda7 video=cyber:800x600-8 60nsram cyberfb_setup: ENTER get_video_mode: ENTER get_video_mode: EXIT - Matched predefined mode cyberfb_setup: default mode: xres=800, yres=600, bpp=8 cyberfb_setup: EXIT amiga_enable_irq: Trying to enable auto-vector IRQ 1 amiga_enable_irq: Trying to enable auto-vector IRQ 3 amiga_enable_irq: Trying to enable auto-vector IRQ 4 amiga_enable_irq: Trying to enable auto-vector IRQ 5 amiga_enable_irq: Trying to enable auto-vector IRQ 7 amiga_enable_irq: Trying to enable auto-vector IRQ 2 amiga_enable_irq: Trying to enable auto-vector IRQ 6 APUS: BATs=1, BUS=66MHz, RAM=60ns, PCI bridge=0 time_init: decrementer frequency = 990000000/60 Console: colour dummy device 80x25 Calibrating delay loop... 460.39 BogoMIPS Memory: 61296k available (1256k kernel code, 512k data, 80k init) [c0000000,c4000000] Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) POSIX conformance testing by UNIFIX Zorro: Probing AutoConfig expansion devices: 3 devices Linux NET4.0 for Linux 2.3 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 4096 bind 4096) Starting kswapd v1.6 cyberfb_init: ENTER amiga_insert_irq: Warning: dev_id of fb vertb handler is zero Console: switching to colour frame buffer device 80x25 fb0: Amiga AGA frame buffer device, using 1280K of video memory pty: 256 Unix98 ptys configured RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: registered device at major 7 loop: enabling 8 loop devices Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide0: Gayle IDE interface (A4000 style) hda: probing with STATUS(0x50) instead of ALTSTATUS(0xe0) hda: WDC AC313000R, ATA DISK drive hdb: probing with STATUS(0x51) instead of ALTSTATUS(0xe0) hdb: probing with STATUS(0x51) instead of ALTSTATUS(0xe0) hdb: probing with STATUS(0x51) instead of ALTSTATUS(0xe0) hdb: CRD-8240B, ATAPI CDROM drive ide0 at 80dd2020 on irq 0x0000000c hda: 25429824 sectors (13020 MB) w/512KiB Cache, CHS=25228/16/63 hdb: ATAPI 24X CD-ROM drive, 128kB Cache Uniform CD-ROM driver Revision: 3.11 Partition check: hda: RDSK hda1 hda2 hda3 hda4 hda5 hda6 hda7 hda8 hda9 hda10 hda11 FD: probing units found fd0 Amiga-builtin serial driver version 4.30 ttyS00 is the amiga builtin serial port Amiga mouse installed. PPP generic driver version 2.4.1 PPP Deflate Compression module registered PPP BSD Compression module registered kmem_create: Forcing size word alignment - nfs_fh VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 80k init Adding Swap: 115916k swap-space (priority -1) nfs warning: mount version older than kernel - glenn |
From: Geert U. <ge...@li...> - 2000-08-02 19:40:53
|
On Wed, 2 Aug 2000, Michel [iso-8859-1] Dänzer wrote: > Alan Buxey wrote: > > > > The kernel just uses amifb:vga even if i tell it to use cyberfb... > > > > > > Looking at drivers/video/fbmem.c, you should try video=cyber:... > > > > all of them should be changed to xxxxfb rather than a mixed bunch. > > standardisation makes sense. What will a name-change mess up? > > AFAIR the idea in 2.4 is to remove the trailing fb from all of them, but let's > wait for Geert's comment on this. I'm a bit reluctant to change them, since such changes cause a lot of bug reports from people used to the old syntax. 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: Geert U. <ge...@li...> - 2000-08-02 19:40:40
|
On Wed, 2 Aug 2000, Arno Griffioen wrote: > > Do the following: look for the APUS #define in drivers/char/vt.c and copy > > the respective chunks to the 2.4 vt.c, et voil_. > > Umm.. Wasn't this the 'very, very wrong m68k approach', which has been > intentionally dropped in 2.3.x/2.4? > > I remember Jes commenting that Linus et al. wouldn't accept this any > longer and that the m68k (and thus APUS) clock handling should be > converted to the way the other platforms work? It should indeed use /dev/rtc. 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: Geert U. <ge...@li...> - 2000-08-02 19:40:05
|
On Wed, 2 Aug 2000, Glenn Hisdal wrote: > On 02-Aug-2000, you wrote: > >> I still can't get the cybervision64 driver to work in 2.4 though (It > >> compiles fine, but I can't use it). > >> The kernel just uses amifb:vga even if i tell it to use cyberfb... > > > Looking at drivers/video/fbmem.c, you should try video=cyber:... > > Yes, that's what I use... (video=cyber:800x600-8) > won't work. Guess I'll have to stick with 2.2.10 a litte longer. Please #define CYBERFBDEBUG in drivers/video/cyberfb.c and tell us more. 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: Geert U. <ge...@li...> - 2000-08-02 19:39:59
|
On Tue, 1 Aug 2000 fh...@at... wrote: > I've added my two Zorro cards to /usr/src/linux/include/zorro.h For > example I added ZORRO_PROD_VMC_HYPERCOM_4_PLUS \ > ZORRO_ID(VMC, 0x06, 0). However, when I compile the kernel > with the new definition and try to use zorro_find the card is not > detected. > i.e. key = zorro_find( ZORRO_PROD_VMC_HYPERCOM_4_PLUS, 0, 0); The board > does not get "found". What have I missed? And it does show up in /proc/bus/zorro (lszorro) with the same ID? /proc/bus/zorro/devices contains a line with 13890600 in the 2nd column? 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: Geert U. <ge...@li...> - 2000-08-02 19:39:57
|
On Tue, 1 Aug 2000 fh...@at... wrote: > I'm going to try the 53c770 driver as memory mapped, when I > compile it that way and try to insert the module I get > undefined symbols readw_l2b, writew_b2l, writel_b2l, and > readl_l2b. Does anyone know what these are? I've assumed > that b2l means "big to little" etc. I'm not totally sure I should get > those errors though because I believe the Power PC and 53c770 are both big > endian. While grep'ing for readw_l2b, I saw that you have to add your own definitions to sym53c8xx_defs.h. It seems like sym53c8xx_defs.h contains support for PIO on PPC only, not for MMIO. Depending on the wanted endiannes (I don't know how the 53c770 is connected to the PPC bus, it could be byte swapped), you should map e.g. writel_b2l() to out_be32() or out_le32(). Note that arguments for writel and out_*32 are in a different order. Good luck! 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: Frank P. <fp...@zu...> - 2000-08-02 11:50:51
|
On Wed, Aug 02, 2000 at 01:19:27PM +0200, Arno Griffioen wrote: > > Do the following: look for the APUS #define in drivers/char/vt.c and copy > > the respective chunks to the 2.4 vt.c, et voil_. > > Umm.. Wasn't this the 'very, very wrong m68k approach', which has been > intentionally dropped in 2.3.x/2.4? I guess so. > I remember Jes commenting that Linus et al. wouldn't accept this any > longer and that the m68k (and thus APUS) clock handling should be > converted to the way the other platforms work? > > AFAIK there was nobody who cared enough to build the driver, so > it got dropped.. I really do not care what Linus thinks in this case (I think he is right), I just want a working solution. Without effort. Yeah, I know, this is the wrong attitude. But as long as this kludge works and there is no proper driver I will use it. -- Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4, CH-8803 Rüschlikon/Switzerland, Tel. +41-1-724-84-42 Fax. +41-1-724-89-56 Business email: fp...@zu... Private email: pe...@he... The opinions expressed here are mine and not necessarily those of IBM. |
From: <gri...@ps...> - 2000-08-02 11:20:01
|
> Do the following: look for the APUS #define in drivers/char/vt.c and copy > the respective chunks to the 2.4 vt.c, et voil_. Umm.. Wasn't this the 'very, very wrong m68k approach', which has been intentionally dropped in 2.3.x/2.4? I remember Jes commenting that Linus et al. wouldn't accept this any longer and that the m68k (and thus APUS) clock handling should be converted to the way the other platforms work? AFAIK there was nobody who cared enough to build the driver, so it got dropped.. Same story as the serial port stuff.. Bye, Arno. -- PSINetworks Europe Fax: +31-23-5699841 | One disk to rule them all, Siriusdreef 34 Tel: +31-23-5699840 | One disk to bind them, 2132WT Hoofddorp+--------------------------------+ One disk to hold the files The Netherlands | * Musical Interlude * | And in the darkness grind 'em ----------------+--------------------------------+------------------------------ We say Retribution, We say Vengeance is bliss, We say Revolution, With a Cast-Iron fist! (Megadeth, 'The Disintegrators') -------------------------------------------------------------------------------- |
From: Glenn H. <gh...@c2...> - 2000-08-02 10:28:16
|
Hello Michel On 02-Aug-2000, you wrote: >> I still can't get the cybervision64 driver to work in 2.4 though (It >> compiles fine, but I can't use it). >> The kernel just uses amifb:vga even if i tell it to use cyberfb... > Looking at drivers/video/fbmem.c, you should try video=cyber:... Yes, that's what I use... (video=cyber:800x600-8) won't work. Guess I'll have to stick with 2.2.10 a litte longer. If I'm lucky, maybe DCE will send some cvisionppc cards to norway soon. I've been waiting for one since January :-( - glenn |
From: Glenn H. <gh...@c2...> - 2000-08-02 10:28:15
|
Hello Ken On 02-Aug-2000, you wrote: >> I got that too. >> Updating to the latest gcc compiler fixed the problem. > What version and where from ? version 2.95.2-1g from ftp://ftp.linuxppc.org/linuxppc-2000/software/ There are some other files that probably needs to be updated to. I remember getting the latest binutils from the same place, and I think there was some other files to. Just try to install it, and if it complains about missing dependencies (or something like that) get the required files here. - glenn |
From: Alan B. <al...@ms...> - 2000-08-02 10:09:01
|
hi, > AFAIR the idea in 2.4 is to remove the trailing fb from all of them, but let's > wait for Geert's comment on this. :-) either way, it'll be standardisation alan |
From: Michel <da...@re...> - 2000-08-02 09:35:02
|
Alan Buxey wrote: > > > The kernel just uses amifb:vga even if i tell it to use cyberfb... > > > > Looking at drivers/video/fbmem.c, you should try video=cyber:... > > all of them should be changed to xxxxfb rather than a mixed bunch. > standardisation makes sense. What will a name-change mess up? AFAIR the idea in 2.4 is to remove the trailing fb from all of them, but let's wait for Geert's comment on this. Michel -- Five days a week my body is a temple. The other two, it's an amusement park. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
From: Alan B. <al...@ms...> - 2000-08-02 09:25:32
|
hi, > > The kernel just uses amifb:vga even if i tell it to use cyberfb... > > Looking at drivers/video/fbmem.c, you should try video=cyber:... all of them should be changed to xxxxfb rather than a mixed bunch. standardisation makes sense. What will a name-change mess up? alan |
From: Michel <da...@re...> - 2000-08-02 08:38:04
|
Frank Petzold wrote: > > I have tried to write kernel images to an AFFS partition. If I diff > source and target after writing, I get differences, always. Not so in > 2.2.10. The AFFS partition is ~2G, maybe that is a problem? All I can say is it worked for me with a smaller partition. Curious to hear other's experiences... Michel -- Press every key to continue. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
From: Michel <da...@re...> - 2000-08-02 08:36:41
|
Frank Petzold wrote: > > Sorry, I can't supply patches (I would have to have them cleared by IBM > first) but I have managed to get hardware clock support in 2.4. Can't you do a CVS commit either? > Do the following: look for the APUS #define in drivers/char/vt.c and copy > the respective chunks to the 2.4 vt.c, et voilà. > > It is one #include (at the top) and some case xxx: in the middle. > > Have fun. I'd call that a 'literate patch' :) Thanks. Michel -- It is easier to fix Unix than to live with NT. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
From: Michel <da...@re...> - 2000-08-02 08:35:26
|
Ken Tyler wrote: > > Ah, Ken had the same problem, also using egcs 1.1.2 . I could build it > > using gcc 2.95.2 . And the kernel even booted! :) > > Is your gcc a 'build it at home in an evening' or from a distribution ? The latest from Debian. The same for binutils. Michel -- So many Christians, so few lions. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
From: Michel <da...@re...> - 2000-08-02 08:33:42
|
Glenn Hisdal wrote: > I still can't get the cybervision64 driver to work in 2.4 though (It > compiles fine, but I can't use it). > The kernel just uses amifb:vga even if i tell it to use cyberfb... Looking at drivers/video/fbmem.c, you should try video=cyber:... Michel -- So many Christians, so few lions. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
From: Michel <da...@re...> - 2000-08-02 08:30:00
|
fh...@at... wrote: > One problem I've noticed with the built it myself compiler (I don't know > if the problem I will describe comes from there though) is that the > temporary assembler files sometime seem to not get written fully or are > corrupted by the compiler before the assembler attempts to assemble them. > At least that's the only explanation I can come up with. I get an error > something like invalid assembler instruction or parse error. Restarting > the compile *most* of the time seems to eliminate the error, but not all > the time. Have you tried the -pipe option, which eliminates the temporary files? Michel -- It is easier to fix Unix than to live with NT. ______________________________________________________________________________ Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS |
From: <fp...@zu...> - 2000-08-02 07:05:28
|
Sorry, I can't supply patches (I would have to have them cleared by IBM first) but I have managed to get hardware clock support in 2.4. Do the following: look for the APUS #define in drivers/char/vt.c and copy the respective chunks to the 2.4 vt.c, et voilà. It is one #include (at the top) and some case xxx: in the middle. Have fun. -- Frank Petzold, IBM Zurich Research Laboratory, Säumerstrasse 4, CH-8803 Rüschlikon/Switzerland, Tel. +41-1-724-84-42 Fax. +41-1-724-89-56 Business email: fp...@zu... Private email: pe...@he... The opinions expressed here are mine and not necessarily those of IBM. |