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: Marek S. <ma...@st...> - 2003-07-28 15:11:04
|
Hello Ondrej
On 28.07.03, you wrote:
>>> Hi all, I'v compiled the 2.4.21 kernel myself and ... great, it
>>> works. Yes, I must use the patch suplied by Marek for BVision
>>> working. I have attached the dmesg output.
>> Which one have You used? Changin arch/ppc/platforms/apus_pci.c or
>> arch/ppc/kernel/pci.c?
> I used the commenting line in 'arch/ppc/platforms/apus_pci.c'.
I was asking about this, because I saw some strange lines in your log
("Zorro: Address space collision on device Zorro device 21406500"). Nothing
like that happened on my system and I'm thinking why You have address space
collision.
If there are no objections, I will commit my changes in a few hours.
> I don't remeber how it works in previous version, but would be funny
> if mixer interface (/dev/mixer) with only one control (master volume)
> can be used.
It would be hard to do it (IMHO), because AmigaDMA sound does not support
hardware control of volume...
Regards
--
Marek Szyprowski .. GG:2309080 .. mailto:ma...@am... ..
...... happy AmigaOS, MacOS and Debian/Linux user ........
........... http://march.home.staszic.waw.pl/ ............
|
|
From: Michel <mi...@da...> - 2003-07-28 14:22:11
|
On Mon, 2003-07-28 at 14:24, Michel Dänzer wrote: > On Mon, 2003-07-28 at 14:17, Ondrej Zima wrote: > > > > BTW: can be used some more sofisticated mailing-list options? In > > message subject would be the prefix as [APUS-dev] or [APUS-user] and > > in reply-to would be the lin...@li... or > > lin...@li.... It prevent to posting only to > > private mail. > > Definitely not, [...] Let me clarify this. I'll never clobber the Reply-To header on any list I administrate, unless there's a very compelling reason which outweighs the disadvantages. As for the subject tags, those can be added or filtered out by everyone, so I guess the majority wins there. Opinions? :) -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer |
|
From: Michel <mi...@da...> - 2003-07-28 12:24:23
|
On Mon, 2003-07-28 at 14:17, Ondrej Zima wrote: > > BTW: can be used some more sofisticated mailing-list options? In > message subject would be the prefix as [APUS-dev] or [APUS-user] and > in reply-to would be the lin...@li... or > lin...@li.... It prevent to posting only to > private mail. Definitely not, google for 'Reply-To munging considered harmful'. The subject doesn't need to be spammed with tags for filtering either. I suggest you use a better MUA. -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer |
|
From: Ondrej Z. <ami...@vo...> - 2003-07-28 12:17:22
|
Marek Szyprowski napsal(a): >> Hi all, I'v compiled the 2.4.21 kernel myself and ... great, it >> works. Yes, I must use the patch suplied by Marek for BVision >> working. I have attached the dmesg output. > Which one have You used? Changin arch/ppc/platforms/apus_pci.c or > arch/ppc/kernel/pci.c? I used the commenting line in 'arch/ppc/platforms/apus_pci.c'. >> In the output is this message: "Memory resource not set for host >> bridge 0" Is this right? > Yes. This is correct. > >> And as you can see, the apne driver works for me :-))) GREAT. > Thanks. > > >> Some more questions: 1) I have installed the dmasound_paula and >> try to play some mp3 files. The result is kernel panic with 60 >> seconds delay to reboot. I didn't make the debug output so I cant >> send it. Is there some misfunctionalities in Amiga DMA sound >> driver? In Gnome sesion, I have always the message the mixer >> cannot be opened. > Today I also noticed that. :( AmigaDMA sound seems to be > misfunctional now. One more bug to trace... I don't remeber how it works in previous version, but would be funny if mixer interface (/dev/mixer) with only one control (master volume) can be used. BTW: can be used some more sofisticated mailing-list options? In message subject would be the prefix as [APUS-dev] or [APUS-user] and in reply-to would be the lin...@li... or lin...@li.... It prevent to posting only to private mail. -- Ondrej Zima <ami...@vo...> Member of Czech ATO - Amiga Translators Organization |
|
From: Ondrej Z. <ami...@vo...> - 2003-07-28 09:56:26
|
Hi all, I'v compiled the 2.4.21 kernel myself and ... great, it works. Yes, I must use the patch suplied by Marek for BVision working. I have attached the dmesg output. In the output is this message: "Memory resource not set for host bridge 0" Is this right? And as you can see, the apne driver works for me :-))) GREAT. Some more questions: 1) I have installed the dmasound_paula and try to play some mp3 files. The result is kernel panic with 60 seconds delay to reboot. I didn't make the debug output so I cant send it. Is there some misfunctionalities in Amiga DMA sound driver? In Gnome sesion, I have always the message the mixer cannot be opened. 2) In which stage the FastATA driver is? -- Ondrej Zima <ami...@vo...> Member of Czech ATO - Amiga Translators Organization |
|
From: Marek S. <ma...@st...> - 2003-07-27 21:14:31
|
Hello Geert
On 25.07.03, you wrote:
>> And the last, but strange thing: in 2.4.21 the tilda ("~") key is not
>> working. It looks like that this key don't generate any code?? Any ideas?
> No idea. But note that the scancode/keycode for ~ on Amiga is 0, which may
> be handled specially somewhere (PC keyboards don't have keycode 0).
Any ideas where to look for that? I tried in drivers/char/ but didn't find
anything really different between 2.4.18 and 2.4.21.
> BTW, did you enable the new input subsystem?
I tried both with new input subsystem (CONFIG_INPUT=y and
CONFIG_INPUT_KEYBDEV=y) and without.
Regards
--
Marek Szyprowski .. GG:2309080 .. mailto:ma...@am... ..
...... happy AmigaOS, MacOS and Debian/Linux user ........
........... http://march.home.staszic.waw.pl/ ............
|
|
From: Marek S. <ma...@st...> - 2003-07-27 21:07:42
|
Hello a.l...@lb... On 27.07.03, you wrote: > right. we need to get this PCI thing done properly because of the PCI Bus > support (Mediator, GREX, Prometheus) as well. good to take step 1 right > now :-) > what errors are you now getting on startup for PCI after doing the > commenting out? PCI subsystem tries to do some other things, when allocating resource fails. All of that of course fail as well. But actually I think that this doesn't matter any more, because I found the "pretty" way of solving this problem. I posted another mail describing that. >> last_ipl[2] already set to 2f, now 2d! >> 24814: 3 -3 2 -2 2 -2 3 -3 2 -2 2 -2 2 3 -3 2 > i see we're still hitting IRQs in weird ways Yes, but I noticed that this has no impact on anything. Maybe because I don't use IDE? As I noticed this is being suspected to cause problems with IDE in A1200? Regards -- Marek Szyprowski .. GG:2309080 .. mailto:ma...@am... .. ...... happy AmigaOS, MacOS and Debian/Linux user ........ ........... http://march.home.staszic.waw.pl/ ............ |
|
From: Marek S. <ma...@st...> - 2003-07-27 09:28:25
|
Hej Marek! Dnia 27.07.03, w Twoim li=B6cie znalaz=B3em nast=EApuj=B1cy fragment: > I found where is the source of this problem!!!! This is/was a very long > night ;) > There are (IMHO) 2 ways of fixing this bug: > 1. remove/comment whole code which "reparents" the resources (ugly way) > 2. add some code to apus_pci.c, which will set-up the pci-bridge proper= ly, > that it's won't cause these problems (pretty way) > Actually I don't know how to do the second. New day - new fresh mind. Today morning I found a pretty way to fix this problem.=20 In arch/ppc/platforms/apus_pci.c the resource region with P2 Mem is being allocated two times (so it fails during the second allocation): first tim= e in apus_pcibios_fixup(), second in apus_pcibios_fixup_bus() (this funtion assigns P2 Mem resource to the bus and later other PCI functions try to allocate it). I simply removed (commented out) resource allocation from apus_pcibios_fixup() and now everything work fine without touching the generic pci code. :)) Could I commit this patch, or do You have any questions/advices? I removed the second bug - which bug will be the next? ;) Regards --=20 Marek Szyprowski .. GG:2309080 .. mailto:ma...@am... .. ...... happy AmigaOS, MacOS and Debian/Linux user ........ ........... http://march.home.staszic.waw.pl/ ............ |
|
From: Marek S. <ma...@st...> - 2003-07-27 00:52:52
|
Hello Geert
On 26.07.03, you wrote:
> In kernel/resoure.c:request_resource(), print the contents of the passed
> `root' and `new' resources. The routine will fail if new isn't a subset of
> root, but you want to know why it happens.
I found where is the source of this problem!!!! This is/was a very long
night ;)
In 2.4.21 (or maybe earlier, but after 2.4.18) there is a new code in PCI
drivers. This code tries to "reparent" resources, that failed to allocate
(arch/ppc/kernel/pci.c, line 343). This happens to the "bridge resource" of
PM2 bridge ("PCI: Cannot allocate resource region 1 of PCI bridge 0" line
in log from kernel 2.4.18). In 2.4.21 when allocating this resource region
fails, kernel tries to "reparent" it (whatever this means) - line "PCI:
reparented B/CVisionPPC PCI mem [e0000000..fffc0000] under B/CVisionPPC PCI
mem" line in 2.4.21 log.
There are (IMHO) 2 ways of fixing this bug:
1. remove/comment whole code which "reparents" the resources (ugly way)
2. add some code to apus_pci.c, which will set-up the pci-bridge properly,
that it's won't cause these problems (pretty way)
Actually I don't know how to do the second. I simply commented out the line
from arch/ppc/kernel/pci.c, but that caused other errors during startup.
However the pm2fb driver and XFree with glint are working now. :)))
Regards
Ps.
I attached dmesg log from both kernels: 2.4.{18,21}
In 2.4.21 the DEBUG in apus_pci.c was disabled, so don't be surprised, that
there is less debug stuff.
--
Marek Szyprowski .. GG:2309080 .. mailto:ma...@am... ..
...... happy AmigaOS, MacOS and Debian/Linux user ........
........... http://march.home.staszic.waw.pl/ ............
|
|
From: Marek S. <ma...@st...> - 2003-07-26 21:47:27
|
Hello Michel On 26.07.03, you wrote: >>> Even with Option "UseFBDev"? >> Yes. Adding this option doesn't change anything. I attached my XF86Config >> and log from XFree. > Well, I don't see anything like 'no PCI board found'. Sorry. Maybe I saw that message before disabling "BusID" option. > Have you tried one > of the example XF86Config-4s in the linux-apus.sf.net contrib section, > or at least not loading superfluous and potentially harmful modules like > int10 and vbe? I've tried all of above and none helped. I even disabled all modules. :( Regards -- Marek Szyprowski .. GG:2309080 .. mailto:ma...@am... .. ...... happy AmigaOS, MacOS and Debian/Linux user ........ ........... http://march.home.staszic.waw.pl/ ............ |
|
From: Michel <mi...@da...> - 2003-07-26 15:03:48
|
On Sat, 2003-07-26 at 13:51, Marek Szyprowski wrote: > > On 26.07.03, you wrote: > > >>> does this rely on the default PCI enabling for the APUS kernel - thats > >>> been disabled by default since 2.4.18 later updates. > > Well, I merely disabled CONFIG_PCI_PERMEDIA in the binaries, Marek is > > obviously building his own kernels with it enabled. > > True. What was the reason for disabling P2-PCI in the binaries? It tends to cause problems with other hardware expansions. > >> I think yes. On kernel without P2-PCI XFree86 can be used only though > >> "fbdev" driver, which is very slow. Glint doesn't work at all (even after > >> removing the "BusID" option from config there is a lot of unresolved > >> symbols and driver quits with message "no pci board found" or something > >> simmilar). > > > Even with Option "UseFBDev"? > > Yes. Adding this option doesn't change anything. I attached my XF86Config > and log from XFree. Well, I don't see anything like 'no PCI board found'. Have you tried one of the example XF86Config-4s in the linux-apus.sf.net contrib section, or at least not loading superfluous and potentially harmful modules like int10 and vbe? -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer |
|
From: Marek S. <ma...@st...> - 2003-07-26 14:21:21
|
Hello Michel On 26.07.03, you wrote: >>> does this rely on the default PCI enabling for the APUS kernel - thats >>> been disabled by default since 2.4.18 later updates. > Well, I merely disabled CONFIG_PCI_PERMEDIA in the binaries, Marek is > obviously building his own kernels with it enabled. True. What was the reason for disabling P2-PCI in the binaries? >> I think yes. On kernel without P2-PCI XFree86 can be used only though >> "fbdev" driver, which is very slow. Glint doesn't work at all (even after >> removing the "BusID" option from config there is a lot of unresolved >> symbols and driver quits with message "no pci board found" or something >> simmilar). > Even with Option "UseFBDev"? Yes. Adding this option doesn't change anything. I attached my XF86Config and log from XFree. Regards -- Marek Szyprowski .. GG:2309080 .. mailto:ma...@am... .. ...... happy AmigaOS, MacOS and Debian/Linux user ........ ........... http://march.home.staszic.waw.pl/ ............ |
|
From: Geert U. <ge...@li...> - 2003-07-26 14:15:14
|
On Sat, 26 Jul 2003, Marek Szyprowski wrote:
> On 25.07.03, you wrote:
> >> I looked though the code, but didn't find anything suspicious. The only
> >> difference is that 2.4.21 starts allocating from resource region 0, while
> >> 2.4.18 started allocaction from resource region 1. Could it be a problem?
> >> Where could I change it?
>
> > Check which resource is used as the parent resource. Probably the PCI
> > resources don't lie completely within the passed parent.
>
> OK, but how can I do this? Sorry, but I know nothing about Linux PCI system
> and everything around it is mysterious for me.
In kernel/resoure.c:request_resource(), print the contents of the passed `root'
and `new' resources. The routine will fail if new isn't a subset of root, but
you want to know why it happens.
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 <mi...@da...> - 2003-07-26 10:15:32
|
On Sat, 2003-07-26 at 11:12, Marek Szyprowski wrote: > Hello a.l...@lb... > > On 25.07.03, you wrote: > > >> The second disfunctional thing in 2.4.21 is the Permedia2-PCI. > > > does this rely on the default PCI enabling for the APUS kernel - thats > > been disabled by default since 2.4.18 later updates. Well, I merely disabled CONFIG_PCI_PERMEDIA in the binaries, Marek is obviously building his own kernels with it enabled. > > does this now stop usage of the Permedia2 ? > > I think yes. On kernel without P2-PCI XFree86 can be used only though > "fbdev" driver, which is very slow. Glint doesn't work at all (even after > removing the "BusID" option from config there is a lot of unresolved > symbols and driver quits with message "no pci board found" or something > simmilar). Even with Option "UseFBDev"? -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer |
|
From: Marek S. <ma...@st...> - 2003-07-26 08:16:14
|
Hello a.l...@lb... On 25.07.03, you wrote: >> The second disfunctional thing in 2.4.21 is the Permedia2-PCI. > does this rely on the default PCI enabling for the APUS kernel - thats > been disabled by default since 2.4.18 later updates. does this now stop > usage of the Permedia2 ? I think yes. On kernel without P2-PCI XFree86 can be used only though "fbdev" driver, which is very slow. Glint doesn't work at all (even after removing the "BusID" option from config there is a lot of unresolved symbols and driver quits with message "no pci board found" or something simmilar). > now my systems back online (thanks to a nice PPP gateway to a NetBSD box > which then feeds to my gateway...) and my hardware is stabilised i'll get > back to work with other things. (i dont have PCMCIA anymore so cant test > your APNE fixes sorry! and with P-to-P PPP i'm giving the serial driver > and the PPP stuff a good working over... reports are we have problems in > this issue). The real problems with serial driver started in 2.4.18 or 2.4.17, on earlier kernels serial driver worked very nice (I used it to exchange data between my Amiga and x86 laptop). Regards -- Marek Szyprowski .. GG:2309080 .. mailto:ma...@am... .. ...... happy AmigaOS, MacOS and Debian/Linux user ........ ........... http://march.home.staszic.waw.pl/ ............ |
|
From: Marek S. <ma...@st...> - 2003-07-26 08:16:14
|
Hello Geert On 25.07.03, you wrote: >> I looked though the code, but didn't find anything suspicious. The only >> difference is that 2.4.21 starts allocating from resource region 0, while >> 2.4.18 started allocaction from resource region 1. Could it be a problem? >> Where could I change it? > Check which resource is used as the parent resource. Probably the PCI > resources don't lie completely within the passed parent. OK, but how can I do this? Sorry, but I know nothing about Linux PCI system and everything around it is mysterious for me. Regards -- Marek Szyprowski .. GG:2309080 .. mailto:ma...@am... .. ...... happy AmigaOS, MacOS and Debian/Linux user ........ ........... http://march.home.staszic.waw.pl/ ............ |
|
From: Geert U. <ge...@li...> - 2003-07-25 00:29:24
|
On Fri, 25 Jul 2003, Marek Szyprowski wrote:
> The second disfunctional thing in 2.4.21 is the Permedia2-PCI.
>
> Log from 2.4.18, where P2-PCI was working:
> ---->8----
> PCI: Probing PCI hardware
> Memory resource not set for host bridge 0
> apus_pcibios_fixup: PCI mem resource requested
> PCI: Cannot allocate resource region 1 of PCI bridge 0
> PCI: resource is e0000000..fffc0000 (200), parent c01a2c2c
> PCI:00:01.0: Resource 0: ef000000-ef01ffff (f=200)
> PCI:00:01.0: Resource 1: e0000000-e07fffff (f=200)
> PCI:00:01.0: Resource 2: e1000000-e17fffff (f=200)
> PCI: Switching off ROM of 00:01.0
> ---->8----
>
> Same part from 2.4.21 - P2-PCI is not working:
> ---->8----
> PCI: Probing PCI hardware
> Memory resource not set for host bridge 0
> apus_pcibios_fixup: PCI mem resource requested
> PCI: Cannot allocate resource region 0 of device 00:01.0
> PCI: Cannot allocate resource region 1 of device 00:01.0
> PCI: Cannot allocate resource region 2 of device 00:01.0
> PCI: Failed to allocate resource 0(fffe0000-fffc0000) for 00:01.0
> PCI: Failed to allocate resource 1(0-7fffff) for 00:01.0
> PCI: Failed to allocate resource 2(0-7fffff) for 00:01.0
> ---->8----
>
> I looked though the code, but didn't find anything suspicious. The only
> difference is that 2.4.21 starts allocating from resource region 0, while
> 2.4.18 started allocaction from resource region 1. Could it be a problem?
> Where could I change it?
Check which resource is used as the parent resource. Probably the PCI resources
don't lie completely within the passed parent.
> And the last, but strange thing: in 2.4.21 the tilda ("~") key is not
> working. It looks like that this key don't generate any code?? Any ideas?
No idea. But note that the scancode/keycode for ~ on Amiga is 0, which may be
handled specially somewhere (PC keyboards don't have keycode 0). BTW, did you
enable the new input subsystem?
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: Marek S. <ma...@st...> - 2003-07-24 23:47:47
|
Hi!
Recently I got new internet connection (wireless lan), so I was able to
download the recent kernel source. As You noticed, I added some missing
Amiga-PCMCIA-ISA code to ppc io code, so now the Apne driver is working
again.
The second disfunctional thing in 2.4.21 is the Permedia2-PCI.
Log from 2.4.18, where P2-PCI was working:
---->8----
PCI: Probing PCI hardware
Memory resource not set for host bridge 0
apus_pcibios_fixup: PCI mem resource requested
PCI: Cannot allocate resource region 1 of PCI bridge 0
PCI: resource is e0000000..fffc0000 (200), parent c01a2c2c
PCI:00:01.0: Resource 0: ef000000-ef01ffff (f=200)
PCI:00:01.0: Resource 1: e0000000-e07fffff (f=200)
PCI:00:01.0: Resource 2: e1000000-e17fffff (f=200)
PCI: Switching off ROM of 00:01.0
---->8----
Same part from 2.4.21 - P2-PCI is not working:
---->8----
PCI: Probing PCI hardware
Memory resource not set for host bridge 0
apus_pcibios_fixup: PCI mem resource requested
PCI: Cannot allocate resource region 0 of device 00:01.0
PCI: Cannot allocate resource region 1 of device 00:01.0
PCI: Cannot allocate resource region 2 of device 00:01.0
PCI: Failed to allocate resource 0(fffe0000-fffc0000) for 00:01.0
PCI: Failed to allocate resource 1(0-7fffff) for 00:01.0
PCI: Failed to allocate resource 2(0-7fffff) for 00:01.0
---->8----
I looked though the code, but didn't find anything suspicious. The only
difference is that 2.4.21 starts allocating from resource region 0, while
2.4.18 started allocaction from resource region 1. Could it be a problem?
Where could I change it?
And the last, but strange thing: in 2.4.21 the tilda ("~") key is not
working. It looks like that this key don't generate any code?? Any ideas?
Regards
--
Marek Szyprowski .. GG:2309080 .. mailto:ma...@am... ..
...... happy AmigaOS, MacOS and Debian/Linux user ........
........... http://march.home.staszic.waw.pl/ ............
|
|
From: Joerg D. <jo...@do...> - 2003-07-24 14:06:15
|
On Tue, Jul 22, 2003 at 06:03:39PM +0200, Roman Zippel wrote: >=20 > I did some lilo hacking lately (more than I actually wanted :) ) and ther= e=20 > is now a new release at http://www.xs4all.nl/~zippel/amiga-lilo-2.3.tar.gz Great! Would you mindi putting it into the cvs-repository as well? Bye, Joerg |
|
From: Marek S. <mar...@us...> - 2003-07-23 08:43:41
|
CVSROOT: /cvsroot/linux-apus
Module name: 2.3
Repository: 2.3/include/asm-ppc/
Changes by: march123@sc8-pr-cvs1. 03/07/23 01:43:40
Log message:
Add Amiga-PCMCIA-ISA specific IO to fix the new Apne driver
Modified files:
2.3/include/asm-ppc/:
io.h
Revision Changes Path
1.15 +16 -0 2.3/include/asm-ppc/io.h
|
|
From: Roman Z. <zi...@li...> - 2003-07-22 16:03:59
|
Hi, I did some lilo hacking lately (more than I actually wanted :) ) and there is now a new release at http://www.xs4all.nl/~zippel/amiga-lilo-2.3.tar.gz Besides smaller bug fixes and updates to make it compile again I added some new features: - support for disk larger than 4GB (if your os supports it, mine doesn't, but I only noticed that, after I was half-ready..., so this is only lightly tested) - basic cross binary support, it's possible to compile a lilo which runs on a different architecture, as there are still endian problems left, it sort of only works for ppc. - it boots an APUS kernel (requires an extra patch for kernel, as the kernel is started via the reset entry) - new keyword 'map', which allows to map an arbitray number of Linux devices to their Amiga devices (replaces 'altdev' which only supported a single mapping). bye, Roman |
|
From: SourceForge.net <no...@so...> - 2003-07-20 18:50:57
|
Bugs item #774653, was opened at 2003-07-20 18:50 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105907&aid=774653&group_id=5907 Category: 2.4 Kernel Group: None Status: Open Resolution: None Priority: 5 Submitted By: Björn Johansson (khelben2) Assigned to: Nobody/Anonymous (nobody) Summary: Serious bug in the serial driver code Initial Comment: Hi! I've tested a lot of 2.4.x kernels and they all suffering from a bug in the serial driver code. With the 2.4.18 and the 2.4.20 the whole system crashes when it tries to connect to my modem which is on /dev/ttyS0. With the 2.4.4 kernel I'm almost able to connect to the internet. What happens is that the modem starts dialing, then just when it's going to connect, the ppp daemon dies. I personally think this is a very serious problem, and I'm considering buying an ADSL ethernet modem to get rid of this problem. But MAYBE there will be problems with this as well? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=105907&aid=774653&group_id=5907 |
|
From: Marek S. <mar...@us...> - 2003-07-19 00:06:54
|
CVSROOT: /cvsroot/linux-apus
Module name: 2.3
Repository: 2.3/include/linux/
Changes by: march123@sc8-pr-cvs1. 03/07/18 17:06:51
Log message:
ASFS driver update to v0.5 (added symlinks support and simple extent cache)
Modified files:
2.3/Documentation/filesystems/:
asfs.txt
2.3/fs/asfs/:
inode.c
2.3/include/linux/:
asfs_fs.h asfs_fs_i.h asfs_fs_sb.h
Revision Changes Path
1.3 +31 -2 2.3/Documentation/filesystems/asfs.txt
1.3 +124 -18 2.3/fs/asfs/inode.c
1.2 +21 -0 2.3/include/linux/asfs_fs.h
1.3 +3 -0 2.3/include/linux/asfs_fs_i.h
1.3 +1 -0 2.3/include/linux/asfs_fs_sb.h
|
|
From: Geert U. <ge...@li...> - 2003-07-11 13:32:39
|
On 11 Jul 2003, Michel [ISO-8859-1] D=E4nzer wrote: > On Fri, 2003-07-11 at 10:30, Geert Uytterhoeven wrote: > > Anonymous Linux/APUS CVS is really flaky these days. Yesterday I fina= lly > > managed to run a cvs update (only once it succeeded)... >=20 > s/Linux\/APUS/sf.net/ >=20 > I keep retrying quickly and it usually works within ten tries. :\ >=20 > Anyway, don't you have developer CVS access to the linux-apus > repository? You're right. I switched to anonymous access a long time ago because I ha= d some problems, but that one indeed seems to work better. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m6= 8k.org 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 <mi...@da...> - 2003-07-11 13:09:41
|
On Fri, 2003-07-11 at 10:30, Geert Uytterhoeven wrote: > > Anonymous Linux/APUS CVS is really flaky these days. Yesterday I finally > managed to run a cvs update (only once it succeeded)... s/Linux\/APUS/sf.net/ I keep retrying quickly and it usually works within ten tries. :\ Anyway, don't you have developer CVS access to the linux-apus repository? -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer |
107 messages has been excluded from this view by a project administrator.
