Menu
▾
▴
linux-apus-devel
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-10-30 23:03:18
|
Hi, On Mon, 30 Oct 2000, Michel Dänzer wrote: > What did you change? I think the problem is that he's using too new a > boothack. pm2fb.c tests for powerup_PCI_present and I took the changes from 2.2, so it might be set now. :) bye, Roman |
|
From: Michel <dae...@st...> - 2000-10-30 22:45:12
|
Roman Zippel wrote: > > Warning: unable to open an initial console. > > Hmm, I don't see a "fb0: ..." line in your output so your card is not > detected at all. I just commited a small change, that should get you > further. What did you change? I think the problem is that he's using too new a boothack. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Roman Z. <zi...@fh...> - 2000-10-30 22:33:12
|
Hi, On Mon, 30 Oct 2000, Reinhard Nissl wrote: > Warning: unable to open an initial console. Hmm, I don't see a "fb0: ..." line in your output so your card is not detected at all. I just commited a small change, that should get you further. > request_module[net-pf-1]: waitpid(5814,...) failed, errno 1 That's unix domain sockets (CONFIG_UNIX), it's always a good idea to keep it compiled in. :) bye, Roman |
|
From: Roman Z. <zi...@us...> - 2000-10-30 22:32:10
|
CVSROOT: /cvsroot/linux-apus Module name: 2.3 Repository: 2.3/include/asm-m68k/ Changes by: zi...@sl.... 00/10/30 14:32:09 Modified files: 2.3/include/asm-m68k/: bootinfo.h Log message: bootinfo fixes |
|
From: Roman Z. <zi...@us...> - 2000-10-30 22:29:45
|
CVSROOT: /cvsroot/linux-apus Module name: 2.3 Repository: 2.3/arch/ppc/amiga/ Changes by: zi...@sl.... 00/10/30 14:29:45 Modified files: 2.3/arch/ppc/amiga/: config.c Log message: bootinfo fixes |
|
From: Reinhard N. <rn...@gm...> - 2000-10-30 20:21:59
|
Hi, Reinhard Nissl wrote: > > Michel Dänzer wrote: > > > > Reinhard Nissl wrote: > > > > > > > CONFIG_PCI=y > > > > > > > > This config is with PCI enabled, so I can't check if pm2fb is enabled. > > > > > > I don't get your answer. Is it ok or is it wrong? > > > > I can't tell because PCI is enabled in your config. I would have liked to > > check if pm2fb is enabled if PCI is disabled. > > Now, I see. I didn't get you, because I wanted to use PCI, while you wanted to > get CVPPC to work without PCI. > > Fine. I'll modify my .config and compile a new kernel. Would you like dmesg > output then? Well, I assume, you would like :-) Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: Michel <dae...@st...> - 2000-10-30 20:11:47
|
Reinhard Nissl wrote: > parse_bootinfo: unknown tag 0x8008 ignored > parse_bootinfo: unknown tag 0x8009 ignored Ah! You're using the latest boothack, right? The 2.4 tree _still_ hasn't got the necessary changes, so you need an old boothack, 990106 worked for me so I included it with the test kernel tarball. This is probably the cause for your problems with or without PCI, because the kernel doesn't know there is a CVisionPPC. > PCI: Probing PCI hardware > NIP: 00000000 XER: 00000000 LR: C000B76C REGS: c032fad0 TRAP: 0400 Granted, it shouldn't panic even in this case :) I'll look into it when I get time, not before next weekend. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Reinhard N. <rn...@gm...> - 2000-10-30 19:38:54
|
Michel Dänzer wrote: > > Reinhard Nissl wrote: > > > > > CONFIG_PCI=y > > > > > > This config is with PCI enabled, so I can't check if pm2fb is enabled. > > > > I don't get your answer. Is it ok or is it wrong? > > I can't tell because PCI is enabled in your config. I would have liked to > check if pm2fb is enabled if PCI is disabled. Now, I see. I didn't get you, because I wanted to use PCI, while you wanted to get CVPPC to work without PCI. Fine. I'll modify my .config and compile a new kernel. Would you like dmesg output then? > > > > CONFIG_FB_PM2=y > > > > CONFIG_FB_PM2_FIFO_DISCONNECT=y > > > > CONFIG_FB_PM2_PCI=y > > > > CONFIG_FB_PM2_CVPPC=y > > > > > > FIFO disconnect doesn't work with our cards. It used to only produce wrong > > > colors for me, but one never knows. > > > > So I'd better start with FIFO disabled? > > Yes, please try that. I'll right now. BTW: attached you'll find the dmesg output after adding kernel option debug=mem. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: Michel <da...@re...> - 2000-10-30 17:47:00
|
Reinhard Nissl wrote: > > > CONFIG_PCI=y > > > > This config is with PCI enabled, so I can't check if pm2fb is enabled. > > I don't get your answer. Is it ok or is it wrong? I can't tell because PCI is enabled in your config. I would have liked to check if pm2fb is enabled if PCI is disabled. > > > CONFIG_FB_PM2=y > > > CONFIG_FB_PM2_FIFO_DISCONNECT=y > > > CONFIG_FB_PM2_PCI=y > > > CONFIG_FB_PM2_CVPPC=y > > > > FIFO disconnect doesn't work with our cards. It used to only produce wrong > > colors for me, but one never knows. > > So I'd better start with FIFO disabled? Yes, please try that. Seems I tend to be too little explicit? Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and the DRI project |
|
From: Reinhard N. <rn...@gm...> - 2000-10-30 17:22:33
|
Hi, Michel Dänzer wrote: > > Reinhard Nissl wrote: > > > > > My first problem is, that when I enable PCI support for Permedia2, the > > > > kernel stops after the first heartbeat (bootmesg indicates, that the > > > > kernel was started), with no output on console. > > > > > > No output at all? What about dmesg? > > > > Nothing. See attached files. > > The boothack line you attached lacks the debug=mem, I suppose you had that > when you tried dmesg? Oops. Will try it again this evening. > > > > When I disable PCI support, I cannot use CVPPC > > > > > > You should be able to (unlike in 2.2), doesn't it work? > > > > No. I don't get a console on CVPPC. > > > > I've attached a couple of files, maybe somethings is wrong with them. > > I've got some remarks, see below. > > > What is a minimalistic AmigaOS configuration to boot linux? > > > > As far as I have tried yet, I get an 0x80000004, when ppcboot_pup is > > starting. > > So how do you boot? :) Nothing about that in this or the user list's archive? Well, I can boot, but some problems could be triggered by running software, that is actually not necessary for booting Linux. Haven't checked the archive yet. > > CONFIG_PCI=y > > This config is with PCI enabled, so I can't check if pm2fb is enabled. I don't get your answer. Is it ok or is it wrong? > > CONFIG_FB_PM2=y > > CONFIG_FB_PM2_FIFO_DISCONNECT=y > > CONFIG_FB_PM2_PCI=y > > CONFIG_FB_PM2_CVPPC=y > > FIFO disconnect doesn't work with our cards. It used to only produce wrong > colors for me, but one never knows. So I'd better start with FIFO disabled? Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: Michel <da...@re...> - 2000-10-30 13:43:53
|
Reinhard Nissl wrote: > > > My first problem is, that when I enable PCI support for Permedia2, the > > > kernel stops after the first heartbeat (bootmesg indicates, that the > > > kernel was started), with no output on console. > > > > No output at all? What about dmesg? > > Nothing. See attached files. The boothack line you attached lacks the debug=mem, I suppose you had that when you tried dmesg? > > > When I disable PCI support, I cannot use CVPPC > > > > You should be able to (unlike in 2.2), doesn't it work? > > No. I don't get a console on CVPPC. > > I've attached a couple of files, maybe somethings is wrong with them. I've got some remarks, see below. > What is a minimalistic AmigaOS configuration to boot linux? > > As far as I have tried yet, I get an 0x80000004, when ppcboot_pup is > starting. So how do you boot? :) Nothing about that in this or the user list's archive? > CONFIG_PCI=y This config is with PCI enabled, so I can't check if pm2fb is enabled. > CONFIG_FB_PM2=y > CONFIG_FB_PM2_FIFO_DISCONNECT=y > CONFIG_FB_PM2_PCI=y > CONFIG_FB_PM2_CVPPC=y FIFO disconnect doesn't work with our cards. It used to only produce wrong colors for me, but one never knows. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and the DRI project |
|
From: Reinhard N. <rn...@gm...> - 2000-10-29 19:11:36
|
Hi, Michel Dänzer wrote: > > Reinhard Nissl wrote: > > > My first problem is, that when I enable PCI support for Permedia2, the > > kernel stops after the first heartbeat (bootmesg indicates, that the kernel > > was started), with no output on console. > > No output at all? What about dmesg? Nothing. See attached files. > > When I disable PCI support, I cannot use CVPPC > > You should be able to (unlike in 2.2), doesn't it work? No. I don't get a console on CVPPC. I've attached a couple of files, maybe somethings is wrong with them. What is a minimalistic AmigaOS configuration to boot linux? As far as I have tried yet, I get an 0x80000004, when ppcboot_pup is starting. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rn...@gm... |
|
From: Michel <dae...@st...> - 2000-10-29 03:27:29
|
Frank Petzold wrote: > > I would like to propose a new bug category: DevKernel. With that we > can seperate bugs in the sable release from work to be done in the dev. > version. > > Therefore I propose a new bug category: DevKernel I've added 'Development Kernel' and 'Other', is that okay? ;) Other suggestions and comments welcome of course. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Michel <dae...@st...> - 2000-10-29 01:31:14
|
Michel Dänzer wrote: > bad news: 53c710 SCSI is broken, this is only a build fix. I hope it > leads someone on the right track No clues? Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Michel <dae...@st...> - 2000-10-29 01:19:08
|
Reinhard Nissl wrote: > My first problem is, that when I enable PCI support for Permedia2, the > kernel stops after the first heartbeat (bootmesg indicates, that the kernel > was started), with no output on console. No output at all? What about dmesg? > When I disable PCI support, I cannot use CVPPC You should be able to (unlike in 2.2), doesn't it work? Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Michel <dae...@st...> - 2000-10-29 01:09:17
|
fh...@at... wrote: > I will try to find time to port it to the 2.2 CVS kernel so that a patch > can be generated as well. That would be great! And our offer for you to join the team and then put the code into CVS yourself still stands ;) > My code is not pretty at the moment (lots of ugly printks and so forth.). I > suppose I should take them out before I make a patch? If they are helpful for debugging (which I assume), please let them in. They can easily be removed afterwards. Michel -- Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast Debian GNU/Linux (powerpc,i386) user \ member of XFree86 and The DRI Project |
|
From: Roman Z. <zi...@fh...> - 2000-10-27 17:03:11
|
Hi, On Thu, 26 Oct 2000 fh...@at... wrote: > I tried posting it to the list but it was too big. :( Did you try to use the patch manager? Otherwise send it to me and I put it on the ftp server. bye, Roman |
|
From: Roman Z. <zi...@fh...> - 2000-10-27 11:18:16
|
Hi, On Fri, 27 Oct 2000, Ken Tyler wrote: > I'll look some more when I catch up on a few things. Please wait one or two weeks, I'm dumping the current block lookup mechanism anyway. bye, Roman |
|
From: Ken T. <ke...@we...> - 2000-10-27 10:27:51
|
On Tue, 3 Oct 2000, Roman Zippel wrote: > Hi, > > > Yep, Ken fixed it AFAIK. > > I see two changes to fs/affs/file.c, but these are also in 2.4. The symptoms in 2.4 don't look at all similar to the 2.2 problem. Started to look at it before I went on holiday but didn't get very far. Couldn't find any consistent pattern to the bad blocks, unlike 2.2 which was very consistent (on big enough files) and was related to the magic number 72. I'll look some more when I catch up on a few things. Ken. |
|
From: Sven O. <ac-...@fr...> - 2000-10-27 06:13:25
|
Hello Geert on 26-Okt-00 wrote Geert Uytterhoeven: > On Wed, 25 Oct 2000, Sven Ottemann wrote: >> is it possibly to use the following functions in a normal programm: >> request_irq, free_irq >> cli, sti >> save_flags, restore_flags ??? > No. The usage of interrupts is limited to the kernel. You should write a > device driver (module) to interface with your user program. This liitle programm should be the preparation for a Prelude(ZII)driver. Regards -- Sve...@St... ac-...@fr... no RISC, no FUN |
|
From: Geert U. <ge...@li...> - 2000-10-26 18:26:07
|
On Wed, 25 Oct 2000, Sven Ottemann wrote:
> is it possibly to use the following functions in a normal programm:
> request_irq, free_irq
> cli, sti
> save_flags, restore_flags ???
No. The usage of interrupts is limited to the kernel. You should write a
device driver (module) to interface with your user program.
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-10-26 11:25:24
|
If anyone would like to look at the driver code I've been working on for 53c770 SCSI, I can mail it to you. I tried posting it to the list but it was too big. :( Currently the driver (evidently) finds the SCSI controller, does the cache test (and passes), and begins trying to setup up the chip for IRQ handling. At that point it stops. My suspicion is that some driver memory space is getting trampled on somehow, because some of the data in the np data structure, is not able to be accessed beyond a certain point in the driver execution. Unfortunately, it has been my experience that memory leaks/problems such as these can be very difficult to track down, especially without a debugger of some sort (or a more experienced coder :)) Another theory I have is that the allocation and alignment of the np structure is being done improperly. Since the np structure is huge and complicated, rewriting this bit would be difficult. I've noticed that the newer versions of the LSI/NCR/Symbios driver code is using a different scheme of allocating and initializing this structure. In any event, I am considering moving my hacking to a new version of the driver code where some of these problems may have been fixed. On the other hand, I could be completely wrong about my suspicions and having some others look at the code might be helpful. I will try to find time to port it to the 2.2 CVS kernel so that a patch can be generated as well. My code is not pretty at the moment (lots of ugly printks and so forth.). I suppose I should take them out before I make a patch? Fred |
|
From: Sven O. <ac-...@fr...> - 2000-10-25 15:31:50
|
Hi, is it possibly to use the following functions in a normal programm: request_irq, free_irq cli, sti save_flags, restore_flags ??? regards Sven -- Sve...@St... ac-...@fr... no RISC, no FUN |
|
From: Geert U. <ge...@li...> - 2000-10-23 20:10:43
|
On Mon, 23 Oct 2000, Roman Zippel wrote:
> On Mon, 23 Oct 2000, Geert Uytterhoeven wrote:
> > > Yeap. :( The other problem is right now I don't _think_ any of the APUS people
> > > are on this list. Perhaps we should get one or two on here (As I understand it
> > > what they need for 2.4 is minimal, but I dont follow too closely) or at least
> > > CC them in this discussion.
> >
> > Indeed. I'm the `closest' to an APUS developer on this list, I think (I have
> > an m68k Amiga and a PPC LongTrail, but not in one box :-).
>
> There is another mailing list for the bitkeeper tree? I didn't know that..
> How do I subscribe?
By getting write access to the bitkeeper tree :-)
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: Roman Z. <zi...@fh...> - 2000-10-23 18:48:23
|
Hi, On Mon, 23 Oct 2000, Geert Uytterhoeven wrote: > > Yeap. :( The other problem is right now I don't _think_ any of the APUS people > > are on this list. Perhaps we should get one or two on here (As I understand it > > what they need for 2.4 is minimal, but I dont follow too closely) or at least > > CC them in this discussion. > > Indeed. I'm the `closest' to an APUS developer on this list, I think (I have > an m68k Amiga and a PPC LongTrail, but not in one box :-). There is another mailing list for the bitkeeper tree? I didn't know that.. How do I subscribe? bye, Roman |
107 messages has been excluded from this view by a project administrator.
