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: Michel <dae...@st...> - 2000-09-29 14:58:04
|
Hi I'd like to inform you that the Linux/APUS project has moved to SourceForge. The starting page is http://linux-apus.sourceforge.net, where links to all important areas (mailing lists, installers for LinuxPPC, ...) can be found. The stuff at sunsite.auc.dk that you mention on your site is obsolete and will disappear sooner or later. It would be nice if you could update the information, TIA 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-09-29 08:09:44
|
Michel Dänzer wrote: > > CVSROOT: /cvsroot/linux-apus > Module name: 2.3 > Repository: 2.3/arch/ppc/ > Changes by: mda...@sl.... 00/09/26 08:35:52 > > Modified files: > 2.3/arch/ppc/: config.in > > Log message: > disable PCI for now to stop confusion and grief Holy sh**, this took long to get to the list... Anyway, for work I've enhanced the scripts to generate these notices so that they can include a diff of the modified files. I could start another support request to get them updated on SourceForge, but only if there is demand. 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-09-29 07:58:19
|
Geert Uytterhoeven wrote: > > Is anyone working on integrating the changes in the APUS tree into Linus' > tree? Don't think so. The best way might be via bitkeeper, but noone here has write permission there. > For my personal interest, I'm mainly thinking about the Amiga specific > parts. Do you want to get your stuff in here as m68k is more or less dead? ;^) 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: Geert U. <ge...@li...> - 2000-09-28 18:45:12
|
Is anyone working on integrating the changes in the APUS tree into Linus'
tree?
For my personal interest, I'm mainly thinking about the Amiga specific parts.
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-09-28 11:47:29
|
Was the Amiga memory map posted to this list? I sent a message to Ralph asking about how the 53c770 chip accesses the Amigas memory and he gave a rather short answer saying it can DMA to all the Amigas memory using big endian '040 bus protocol. I'm sure that is a complete answer that tells me all I need to know. Does that mean the chips sees the Amiga in a flat linear memory space. i.e. can see all chip/custom chip and fast ram and would access it just like a 68040 chip. i.e. the locations would be the same numerically. Another i.e. if a custom chip or memory location were at $DDXYWZ00 to the 68040 if would appear the same to the SCSI chip? If anyone can point me to a message or FAQ that describes the Amigas memory layout relative to the processor I would appreciate it. Fred |
|
From: Sven L. <lu...@dp...> - 2000-09-28 10:31:37
|
On Tue, Sep 26, 2000 at 03:39:10PM +0100, Alan Buxey wrote:
> hi,
>
> > Learning by doing is still the best paradigm I know :)
>
> :-) Well, I've got the way to tag the branch... now its just getting the
> single files updated :-)
>
> 2 months ago (CVS == #undef), now (CVS == 'Hello World') wont be long
> until (Alan != struct {newbie})
>
> > No, Jesper removed it in early 2.2 when the kernel booted reliably on all
> > hardware AFAIR.
>
> I'll take a look at the stuff on FTP and see what I need to pull in to get
> APUS_PROGRESS working again.
>
Alan, it's mostly the small piece of code which michael sent you in the
previous mail. It works ok, and debugging with it can be lot of fun, needs a
lot of rebooting though.
you need a way to read the address back though. i wrote a little program some
time back that does it, but i guess any memory editor would do it (most asm do
it).
Tell me if you need some help.
Friendly,
Svne LUTHER
|
|
From: Ken T. <ke...@we...> - 2000-09-27 20:31:55
|
On Wed, 27 Sep 2000, Roman Zippel wrote: > > Is affs still broken ? > Sorry for not answering earlier, but I have a week off right now. :-) > I was working on this before I left, but it isn't finished yet, so the cvs > version is still in the same state. Are you getting anywhere with it ? The affs subdir has changed quite a bit since 2.2. I had a look and did some copying tests. The corruption was similar to what was happening in 2.2. Ken. |
|
From: Roman Z. <zi...@fh...> - 2000-09-27 14:01:41
|
Hi, On Thu, 21 Sep 2000, Ken Tyler wrote: > Is affs still broken ? > > If yes, what's wrong with it and how 'dangerous' is it considering my affs > test partition is on the same drive as ext2 partitions. Sorry for not answering earlier, but I have a week off right now. :-) I was working on this before I left, but it isn't finished yet, so the cvs version is still in the same state. bye, Roman |
|
From: <fp...@zu...> - 2000-09-27 12:09:57
|
Under 2.4.0-test7, the floppy driver dies not work. When I try to mount a disk, it starts moveng the head for some minutes, failing to mount. This goes for HD and DD, FFS and VFAT disks. Besides, the parallel driver does not work either. It seems to send corrupted data. -- 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: Ken T. <ke...@we...> - 2000-09-27 09:01:03
|
Hello, As I find the keyboard beeps a bit loud even when listening to Metalica mp3s ;) I came up with this. Is it OK to check the hardware this way or should an in use flag be better ? Ken. --- 2.2_orig/arch/m68k/amiga/amisound.c Fri May 26 05:07:30 2000 +++ 2.2_work/arch/m68k/amiga/amisound.c Tue Sep 26 18:03:22 2000 @@ -63,6 +63,9 @@ if (!snd_data) return; + if (custom.dmaconr & DMAF_AUD2) + return; /* do nothing if ch2 in use */ + save_flags(flags); cli(); del_timer( &sound_timer ); |
|
From: Geert U. <ge...@li...> - 2000-09-26 17:49:15
|
On Mon, 25 Sep 2000, Michael Schmitz wrote:
> > (non-trivial) assignment fbdev <-> pcidev . If you know how to do it easily,
> > patches go to pa...@XF... or fi...@XF..., design suggestions to
> > xp...@XF... :)
>
> Add a fbdev->private field to hold PCI/Zorro/ISA/whatever dependent
> framebuffer information, and an ioctl to retrieve that bit. That's only my
> .01 Euro, and Geert may have reasons not to implement this.
I'd say: why add the ioctl if you can do without it? It's not difficult to
match fbdevs and PCI devs, just look at the addresses.
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: Michel D. <mda...@us...> - 2000-09-26 15:35:55
|
CVSROOT: /cvsroot/linux-apus Module name: 2.3 Repository: 2.3/arch/ppc/ Changes by: mda...@sl.... 00/09/26 08:35:52 Modified files: 2.3/arch/ppc/: config.in Log message: disable PCI for now to stop confusion and grief |
|
From: Michel <da...@re...> - 2000-09-26 15:33:54
|
Robert Ramiega wrote: > > > > > (and if so which bootstrap should i use the new one that's required > > > > > for 2.2.10 kernel or the old one that was kindly included by Michel > > > > > Danzer in 2.4.0-test4 tarball) ? > > > > > > > > Note that PCI doesn't work yet in 2.4 . Guess I should also move that > > > > to a So basicaly for now with 2.4 we are stuck at old bootstrap right > > > > ? > > > > Right, but that's independent of the PCI stuff. Noone has bothered to > > adapt > I just can't get the connection between PCI for Permedia, Permedia support > and bootstrap. It's just that the way information about the PCI bridge is passed by boothack to the kernel has changed in the later boothack versions. The 2.4 kernel hasn't been adapted yet and thus it always thinks there's no Permedia2, so pm2fb doesn't work. > For now i won't be compiling "PCI for Permedia" in.... or maybe not.... i'm > at loss here =o((( _Don't_ compile it in because it o doesn't work (the kernel doesn't even boot for me) o isn't needed for pm2fb (I think I was a bit over-busy to this respect in 2.2, in particular I forgot about the m68k Amigans who don't have PCI yet) > Now i would give almost anything to have 2.4.0 working somewhat stable on my > Amiga (it feels faster a lot) Funny, it seems to be the other way around for most other archs... 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: Robert R. <ro...@pl...> - 2000-09-26 15:15:05
|
On Tue, Sep 26, 2000 at 05:02:57PM +0200, Michel Dänzer wrote: > > permedia, tries to boot generic framebuffer and fails. > > It can't fall back to another driver if the one you want (glint in this case) > fails. Well i was just trying to analyze what's in that log file but i'm no expert at it =o))) > > > > My Amiga just rebooted (i was running selfcompiled 2.4.0-test4) without > > apparent reason > > No kernel panic/oops/whatever either? Nothing! I've never seen it crashing like this before (there are times that it hangs but this time it rebooted cleanly in to AmigaOS). There were 3 users logged but none of them was doing something nasty (ok ok one of them was playin NetHack ;o) There is no trace of crash in any of the logs. > > > > (and if so which bootstrap should i use the new one that's required for > > > > 2.2.10 kernel or the old one that was kindly included by Michel Danzer > > > > in 2.4.0-test4 tarball) ? > > > > > > Note that PCI doesn't work yet in 2.4 . Guess I should also move that to a > > So basicaly for now with 2.4 we are stuck at old bootstrap right ? > > Right, but that's independent of the PCI stuff. Noone has bothered to adapt I just can't get the connection between PCI for Permedia, Permedia support and bootstrap. For now i won't be compiling "PCI for Permedia" in.... or maybe not.... i'm at loss here =o((( Now i would give almost anything to have 2.4.0 working somewhat stable on my Amiga (it feels faster a lot) -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
|
From: Michel <da...@re...> - 2000-09-26 15:03:39
|
Robert Ramiega wrote: > > > Is PCI for Permedia needed in kernel to use X > > > > It shouldn't. If it doesn't work without, that's a bug. > Actually i don't know (i didn't try it.. i just think that XF4 can't find > permedia, tries to boot generic framebuffer and fails. It can't fall back to another driver if the one you want (glint in this case) fails. > My Amiga just rebooted (i was running selfcompiled 2.4.0-test4) without > apparent reason No kernel panic/oops/whatever either? > i start to think that there is something wrong with memory > management under test4 (i had mutt exitting abnormally twice) > > > (and if so which bootstrap should i use the new one that's required for > > > 2.2.10 kernel or the old one that was kindly included by Michel Danzer > > > in 2.4.0-test4 tarball) ? > > > > Note that PCI doesn't work yet in 2.4 . Guess I should also move that to a > So basicaly for now with 2.4 we are stuck at old bootstrap right ? Right, but that's independent of the PCI stuff. Noone has bothered to adapt 2.4 to the latest boothack yet (BTW I wonder if Nicholai is still around somewhere?). 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 <da...@re...> - 2000-09-26 14:59:42
|
Alan Buxey wrote: > > Not in the trunk please. It's fine in the branch, but we'll have to > > remember taking it out before merging to the trunk. > > can we have another branch....and then pull it in when needed? Why another branch? Isn't one branch enough for MOL development? ;) > I'm sorry, but i still dont understand how the branch pulling/pushing works > in practice (ie how the new ppc_ksyms.c in the MOL branch will be related to > the ppc_ksyms.c in the main trunk) They'll be independent of each other. You can break whatever you want in the branch without affecting the trunk and vice versa. It is however always possible to merge changes from one to the other. When the branch has reached stability, we will merge it into the trunk completely and will stop working on it. 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: Alan B. <al...@ms...> - 2000-09-26 14:40:23
|
hi,
> Learning by doing is still the best paradigm I know :)
:-) Well, I've got the way to tag the branch... now its just getting the
single files updated :-)
2 months ago (CVS == #undef), now (CVS == 'Hello World') wont be long
until (Alan != struct {newbie})
> No, Jesper removed it in early 2.2 when the kernel booted reliably on all
> hardware AFAIR.
I'll take a look at the stuff on FTP and see what I need to pull in to get
APUS_PROGRESS working again.
> Not in the trunk please. It's fine in the branch, but we'll have to remember
> taking it out before merging to the trunk.
can we have another branch....and then pull it in when needed? I'm sorry,
but i still dont understand how the branch pulling/pushing works in
practice (ie how the new ppc_ksyms.c in the MOL branch will be related to
the ppc_ksyms.c in the main trunk)
alan
|
|
From: Robert R. <ro...@pl...> - 2000-09-26 14:23:09
|
On Tue, Sep 26, 2000 at 03:31:47PM +0200, Michel Dänzer wrote: > > Possible, but it never hurts to try. Well possible that my (minor) changes to > those files broke things so badly :( I've looked at the diff and it seemed that there are no big changes (but some constants|macros appeared there so i figured that something had to changed not only in pm2fb but in other files (don;t remember right now as i looked at it some days ago) In the meantime i suspected something wrong with gcc/binutils so i thought i'll rebuild 2.4.0-test4 with included (Your) config file (only thing i changed was including IP aliasing support) > > Is PCI for Permedia needed in kernel to use X > > It shouldn't. If it doesn't work without, that's a bug. Actually i don't know (i didn't try it.. i just think that XF4 can't find permedia, tries to boot generic framebuffer and fails. My Amiga just rebooted (i was running selfcompiled 2.4.0-test4) without apparent reason i start to think that there is something wrong with memory management under test4 (i had mutt exitting abnormally twice) Anyway i'll recompile test5 (and i'll also try it with test4's pm2fb) and see how it goes (i should now it tommorow morning) > > > (and if so which bootstrap should i use the new one that's required for > > 2.2.10 kernel or the old one that was kindly included by Michel Danzer in > > 2.4.0-test4 tarball) ? > > Note that PCI doesn't work yet in 2.4 . Guess I should also move that to a So basicaly for now with 2.4 we are stuck at old bootstrap right ? > branch, unfortunately I don't have time to work at it right now. sounds familiar =o))))) -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
|
From: Michel <da...@re...> - 2000-09-26 13:49:37
|
Alan Buxey wrote: > > I found it in an old m68k diff: > > can you commit that into the CVS 2.2 tree so I can slurp it in tonight? No time, sorry. It's in the oldest (2.2.3pre1) m68k diff which is still in our FTP's obsolete/ . There you also find the original calls from Jesper. Don't forget to cvs upd -r mol-branch before committing anything ;) 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 <da...@re...> - 2000-09-26 13:35:46
|
Alan Buxey wrote: > > I'm creating a MOL branch (again) called mol-branch now. Please commit > > your MOL changes there. > > okay...boy do i need to quickly learn this cvs stuff! :-) Learning by doing is still the best paradigm I know :) > > I see APUS_PROGRESS isn't in our code anymore. Time to dig up some old > > versions... Anyway, what APUS_PROGRESS(n) basically did was write n to a > > fixed memory address (don't remember - something like 0xe0001234 ?) which > > wouldn't be cleared on reboot. You could read that value back with a > > memory viewer in AmigaOS to find out how far the code ran. > > thought it would be that easy...i just couldnt find APUS_PROGRESS() in any > of the code (must have got taken out when we did the move to sourceforge No, Jesper removed it in early 2.2 when the kernel booted reliably on all hardware AFAIR. > (it needed/needs to go back in)) Not in the trunk please. It's fine in the branch, but we'll have to remember taking it out before merging to the trunk. 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: Alan B. <al...@ms...> - 2000-09-26 13:33:05
|
hi, > I found it in an old m68k diff: can you commit that into the CVS 2.2 tree so I can slurp it in tonight? thanks, alan |
|
From: Michel <da...@re...> - 2000-09-26 13:32:41
|
Robert Ramiega wrote: > My question: Is anyone running anything more than 2.4.0-test4 on C/BVision? > If so can i have .config, please? > > I guess that simply copying drivers/video/pm2fb.* from one kernel tree to > another won't work as some changes might be done in other files that affect > this. Possible, but it never hurts to try. Well possible that my (minor) changes to those files broke things so badly :( > The second part is a bit Debian specific i suspect. I've installed 4.0.1 > debs available from Branden Robinson webpage when i;m running 2.4.0-test4 > all i get is signal 11 when trying to start X (i tried both with and without > BusID in XF86Config). Can you send me the log please? > Is PCI for Permedia needed in kernel to use X It shouldn't. If it doesn't work without, that's a bug. > (and if so which bootstrap should i use the new one that's required for > 2.2.10 kernel or the old one that was kindly included by Michel Danzer in > 2.4.0-test4 tarball) ? Note that PCI doesn't work yet in 2.4 . Guess I should also move that to a branch, unfortunately I don't have time to work at it right now. > Other than that all seems fine ;o)))) :) 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: Alan B. <al...@ms...> - 2000-09-26 13:28:09
|
hi, > > I'm creating a MOL branch (again) called mol-branch now. Please commit your > MOL changes there. okay...boy do i need to quickly learn this cvs stuff! :-) > I see APUS_PROGRESS isn't in our code anymore. Time to dig up some old > versions... Anyway, what APUS_PROGRESS(n) basically did was write n to a fixed > memory address (don't remember - something like 0xe0001234 ?) which wouldn't > be cleared on reboot. You could read that value back with a memory viewer in > AmigaOS to find out how far the code ran. thought it would be that easy...i just couldnt find APUS_PROGRESS() in any of the code (must have got taken out when we did the move to sourceforge (it needed/needs to go back in)) I can then work with the Head.S quickly then alan |
|
From: Robert R. <ro...@pl...> - 2000-09-26 13:17:33
|
Hi! After some fighting i managed to boot selfcompiled 2.4.0-test4. I tried to boot test7 and test8 but they didn;t work (bootmesg showed what seems to be normal booting while dmesg showed nothing at all). Right now i'm trying to compile 2.4.0-test5 and see how it behaves. I guess that much of my trouble is caused by some changes in pm2fb but jump from test4 to test8 is just too overhelming to me (diff was just toooooo biiiiig). I also suspect that there might be something more than just that. My question: Is anyone running anything more than 2.4.0-test4 on C/BVision ? If so can i have .config, please? I guess that simply copying drivers/video/pm2fb.* from one kernel tree to another won't work as some changes might be done in other files that affect this. The second part is a bit Debian specific i suspect. I've installed 4.0.1 debs available from Branden Robinson webpage when i;m running 2.4.0-test4 all i get is signal 11 when trying to start X (i tried both with and without BusID in XF86Config). Is PCI for Permedia needed in kernel to use X (and if so which bootstrap should i use the new one that's required for 2.2.10 kernel or the old one that was kindly included by Michel Danzer in 2.4.0-test4 tarball) ? Other than that all seems fine ;o)))) -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
|
From: Michel <da...@re...> - 2000-09-26 12:58:25
|
Michel Dänzer wrote:
>
> Alan Buxey wrote:
>
> > however, though the kernel still compiles, it then crashes
> > upon bootup..this is an ongoing investigation (i now need to do some
> > APUS_PROGRESS calls - but am insufficiently trained to jump straight into
> > this (help! anyone? :-)) )
>
> I see APUS_PROGRESS isn't in our code anymore. Time to dig up some old
> versions... Anyway, what APUS_PROGRESS(n) basically did was write n to a
> fixed memory address (don't remember - something like 0xe0001234 ?) which
> wouldn't be cleared on reboot. You could read that value back with a memory
> viewer in AmigaOS to find out how far the code ran.
I found it in an old m68k diff:
#define APUS_PROGRESS(_a) \
lis r3,0xfff0; \
ori r3,r3,0xeff0; \
lis r4,0x1234; \
ori r4,r4,(_a); \
stw r4,0x0(r3); \
dcbf 0,r3; \
sync; \
isync
So it's 0xeff01234 .
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
|
107 messages has been excluded from this view by a project administrator.
