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: Geert U. <ge...@li...> - 2000-10-17 09:55:19
|
On Mon, 16 Oct 2000, Arno Griffioen wrote:
> Finally dug up the A3000 schematics at home.
>
> This is the list in the schematics document:
>
> $000000 - $1FFFFF Up to 2Megs of CHIP mem
> $200000 - $9FFFFF Auto-Config memory space (Z-II)
> $A00000 - $BFFFFF IO Space (8520s)
> $C00000 - $D7FFFF A500 'ranger' memory
> $D80000 - $D9FFFF Custom chip register mirror or RTC
> $DA0000 - $DBFFFF Unused
> $DC0000 - $DDFFFF RTC
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A3000 builtin SCSI is here as well. As some other misc bits, IIRC.
> $DE0000 - $DFFFFF Custom Chip Registers
DFF000-DFFFFF
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: <gri...@ps...> - 2000-10-16 17:25:29
|
> If anyone can point me to a message or FAQ that describes > the Amigas memory layout relative to the processor I > would appreciate it. Sorry 'bout the delay.. Finally dug up the A3000 schematics at home. This is the list in the schematics document: $000000 - $1FFFFF Up to 2Megs of CHIP mem $200000 - $9FFFFF Auto-Config memory space (Z-II) $A00000 - $BFFFFF IO Space (8520s) $C00000 - $D7FFFF A500 'ranger' memory $D80000 - $D9FFFF Custom chip register mirror or RTC $DA0000 - $DBFFFF Unused $DC0000 - $DDFFFF RTC $DE0000 - $DFFFFF Custom Chip Registers $E00000 - $E7FFFF Unused $E80000 - $E8FFFF Autoconfig Slot $E90000 - $EFFFFF 64K Autoconfig slots $F00000 - $FFFFFF ROM space $01000000 - $07FFFFFF On-board 32 bit RAM. Grows DOWN from $07FFFFFF $08000000 - $0FFFFFFF 32 bit expansion. Grows UP from $08000000 $10000000 - $EFFFFFFF 32 bit 'other' expansion space 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: Michel D. <mda...@us...> - 2000-10-13 18:28:03
|
CVSROOT: /cvsroot/linux-apus Module name: 2.3 Repository: 2.3/arch/ppc/kernel/ Changes by: mda...@sl.... 00/10/13 11:28:02 Modified files: 2.3/drivers/scsi/: 53c7xx.h 2.3/arch/ppc/: config.in 2.3/arch/ppc/kernel/: apus_pci.c Log message: good news: PCI seems to work - maybe it got fixed along with debug=mem bad news: 53c710 SCSI is broken, this is only a build fix. I hope it leads someone on the right track |
|
From: Michel <dae...@st...> - 2000-10-13 16:11:55
|
Robert Ramiega wrote: > > If it's okay with the other developers, please tell us your SF user name > give me a copule of hours so i'll dig it (i have it somewhere on disk of > one machine in here <<and it's like 7 or so of them>>) and i have to leave > now (it should be grey i think) It is, I just found out using the SF people search. > > One of the other admins please add him if I'm already away in vacation > > (leaving tonight). > Please wait till there be something to put and i;ll need to be amongst > developers to put it there... I've just added you, welcome aboard! :) You can also use it for updating the web site, like for announcing IRC channels or whatever ;) > There is no rush and i really don't have total control over my time so i > can't promise anything =o(((( No problem. There will be a delay until you're really added - the infamous SF cron job delay. > I'm looking at input core and am trying to find some spare time.. > (compiling kernel and stuff like that are easy you just push the buttons and > see when and if it will blow =o))) input core requires more attention.... Yes, but I think it could be a good starting point. Let's hope that I'm right. 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-10-13 15:31:28
|
On Fri, Oct 13, 2000 at 02:29:23PM +0200, Michel Dänzer wrote: > Robert Ramiega wrote: > > > i'm preparing myself for some work on input core; i already checkout'ed > > linuxconsole ruby from freshmeat > > You mean sourceforge, right? umm yes... where is my head? > > If it's okay with the other developers, please tell us your SF user name give me a copule of hours so i'll dig it (i have it somewhere on disk of one machine in here <<and it's like 7 or so of them>>) and i have to leave now (it should be grey i think) > Robert and we'll add you to the team. Time for you to start real hacking ;) geee! stop frightening me! =o)))) > One of the other admins please add him if I'm already away in vacation > (leaving tonight). Please wait till there be something to put and i;ll need to be amongst developers to put it there... There is no rush and i really don't have total control over my time so i can't promise anything =o(((( I'm looking at input core and am trying to find some spare time.. (compiling kernel and stuff like that are easy you just push the buttons and see when and if it will blow =o))) input core requires more attention.... -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
|
From: Michel <dae...@st...> - 2000-10-13 12:31:24
|
Robert Ramiega wrote: > i'm preparing myself for some work on input core; i already checkout'ed > linuxconsole ruby from freshmeat You mean sourceforge, right? If it's okay with the other developers, please tell us your SF user name Robert and we'll add you to the team. Time for you to start real hacking ;) One of the other admins please add him if I'm already away in vacation (leaving tonight). 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-13 11:23:42
|
Sven LUTHER wrote: > > Of course, if we'd get PCI working in 2.4 as well it would be best to skip > > the fbdev probing code altogether probably. > > Are there no other hardware without pci using the glint kernel ? I don't know of any - it's a PCI chip, after all. If m68k people want to use it, they can easily implement PCI support as well. > > > Will try to do a pm3 fbdev this weekend. > > > > Good luck, remember that this probably won't help you with this bug as > > it's only about PCI not being available. > > If i compile a kernel without pci support, would it show the bug ? Hopefully, yes. > BTW, i will post a true bresenham accel fundtion for glint chips to > xfree-glint today, maybe you could try it out on the pm2. Or do you know of > a reason why the current accels only do 45° inclined lines ? The only thing I can think of is that the glint chips' line algorithm isn't compatible to Bresenham. 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: Sven L. <lu...@dp...> - 2000-10-13 09:03:21
|
On Wed, Oct 11, 2000 at 06:20:58PM +0200, Michel Dänzer wrote: > Sven LUTHER wrote: > > > > > > > In the attachement You'll find small tgz with my XF86Config and 4 > > > > > > Xfree.log (with some combination of BusID and UseFBDev) I hope that > > > > > > helps. > > > > > > > > > > Interesting. Looks like it always crashes if you specify the bus ID. > > > > > Otherwise, it gets further, but then crashes. Sven, could it be due to > > > > > some of your PM3 changes? > > > > > > > > No this is not possible, all pm3 changes i did test for the the chip to > > > > be a pm3, and i did nothing yet for fbdev use. > > > > > > The problem might be exactly there. If there is no PCI, you can't check > > > the PCI info. I had originally tried to guard all PCI related stuff by the > > > FBDevProbed boolean (maybe we should change that to HavePCI or > > > something?), maybe you accidentally broke the logic with your PM3 changes? > > > > No i think not that i did anything like that, the only stuff i did is > > duplicate the permedia2v case in switches and rename it permedia3 and do > > some modification then. > > > > BTW, maybe the glint driver would need some restructuring, i thinkk. > > Whatever happened to the discution about fbdev probing we had some month ago > > with (don't remember exactly, but he was one of the big xfree guys.) > > I guess you mean Egbert Eich? > > Of course, if we'd get PCI working in 2.4 as well it would be best to skip the > fbdev probing code altogether probably. Are there no other hardware without pci using the glint kernel ? > > Will try to do a pm3 fbdev this weekend. > > Good luck, remember that this probably won't help you with this bug as it's > only about PCI not being available. If i compile a kernel without pci support, would it show the bug ? The truth is, i don't have enough space on my apus harddisk to do Xfree compiles. Maybe i could try erasing all the disk, and doing a minimal install. BTW, i will post a true bresenham accel fundtion for glint chips to xfree-glint today, maybe you could try it out on the pm2. Or do you know of a reason why the current accels only do 45° inclined lines ? Friendly, Sven LUTHER |
|
From: <fp...@zu...> - 2000-10-13 07:04:25
|
On Thu, Oct 12, 2000 at 10:03:33PM +0200, Roman Zippel wrote: > Hi, > > > this time modprobe/depmod doesn;t complain but printouts (small ps file) are > > screwed. > > Hmm, now I can only try to add some prints and see if I find something > suspicious. > Does it work in 2.2? Yes. But there was a time when 2.2 printing showed exactly the same behaviour. I cannot tell what fixed it there. In my case (I have a PS printer): Printing PS does not work, it goes "ignore data" after a while and prints nothing. Iswitched to LaserJet II mode to see what arrived at the printer, that looked OK to me. But it was 10 pages of PS prologue, and I did not read it thoroughly. Anyway, I inserted iobarriers aroung any access on ciab and even a delay loop in the write function. With the iobarriers it seemed to get further until ignoring data, the delay loop did not help at all. I tried all this back in 2.1 when printing did not work, with exactly the same results then. But 2.1 was fixed sometime. I do not remember whom when and how. I suspect the problem is the same as it was in 2.1 (2.2?) -- 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: Roman Z. <zi...@fh...> - 2000-10-12 22:46:26
|
Hi, > Log message: > conflict fixes from import bitkeeper (2.4.0-test9) It compiles, but I'll test it tomorrow because I need some sleep. I don't mind if anyone wants to try it :), but I don't expect major problems. bye, Roman |
|
From: Roman Z. <zi...@us...> - 2000-10-12 22:37:32
|
CVSROOT: /cvsroot/linux-apus Module name: 2.3 Repository: 2.3/drivers/scsi/ Changes by: zi...@sl.... 00/10/12 15:37:30 Modified files: 2.3/drivers/scsi/: a2091.c a2091.h a3000.c a3000.h Log message: compile fixes |
|
From: Robert R. <ro...@pl...> - 2000-10-12 22:32:27
|
Hi! On Thu, Oct 12, 2000 at 10:03:33PM +0200, Roman Zippel wrote: > Hi, > > > this time modprobe/depmod doesn;t complain but printouts (small ps file) are > > screwed. > > Hmm, now I can only try to add some prints and see if I find something > suspicious. i don;t know if this is of any value but after printing text file i always get one page more with just letter E in the upper left corner. When i print something else than text those page with E come out at random (sometimes it's the first page and another one or two at the end of printout; sometimes only after printing and i 2 or 3 copies) > Does it work in 2.2? Yes. It works perfectly. > > > AGAINST-2.4.0-test9 in there) > > I'm just importing it. :-) Wow! Great! thanks! -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
|
From: Roman Z. <zi...@us...> - 2000-10-12 22:10:19
|
CVSROOT: /cvsroot/linux-apus Module name: 2.3 Repository: 2.3/mm/ Changes by: zi...@sl.... 00/10/12 15:10:18 Modified files: ./: Makefile 2.3/Documentation/: Configure.help 2.3/arch/m68k/: config.in 2.3/arch/ppc/: config.in 2.3/arch/ppc/kernel/: apus_setup.c head.S ppc-stub.c ppc_ksyms.c time.c 2.3/arch/ppc/mm/: init.c 2.3/drivers/char/: Makefile 2.3/drivers/scsi/: Config.in a2091.c a3000.c blz1230.c blz2060.c cyberstorm.c cyberstormII.c fastlane.c gvp11.c oktagon_esp.c 2.3/mm/: page_alloc.c Log message: conflict fixes from import bitkeeper (2.4.0-test9) |
|
From: Roman Z. <zi...@fh...> - 2000-10-12 20:14:45
|
Hi, > this time modprobe/depmod doesn;t complain but printouts (small ps file) are > screwed. Hmm, now I can only try to add some prints and see if I find something suspicious. Does it work in 2.2? > Does order of modeprobing matter? No. > quick question: > do You plan to import test9 anytime soon? (reason i'm asking is that i'm > preparing myself for some work on input core; i already checkout'ed > linuxconsole ruby from freshmeat and i noted that there is a file > AGAINST-2.4.0-test9 in there) I'm just importing it. :-) (Actually it's test10-pre1, but there aren't that much changes.) bye, Roman |
|
From: Robert R. <ro...@pl...> - 2000-10-12 09:37:12
|
On Thu, Oct 12, 2000 at 09:56:23AM +0200, Roman Zippel wrote: > > modprobe parport_amiga > > /lib/modules/2.4.0-test8/kernel/drivers/parport/parport_amiga.o: unresolved symbol iobarrier_rw > > Sorry, I should have tried to compile it. Should be fixed now. no problem =o)) it happens =o))) this time modprobe/depmod doesn;t complain but printouts (small ps file) are screwed. Does order of modeprobing matter? (i first modeprobed parport, then parport_amiga and then lp) I don't think so but.... quick question: do You plan to import test9 anytime soon? (reason i'm asking is that i'm preparing myself for some work on input core; i already checkout'ed linuxconsole ruby from freshmeat and i noted that there is a file AGAINST-2.4.0-test9 in there) -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
|
From: Roman Z. <zi...@fh...> - 2000-10-12 08:02:18
|
Hi, On Thu, 12 Oct 2000, Robert Ramiega wrote: > I recompiled only the modules (i had all that was related to parallel port > as modules in my .config) and here is what i got: > > modprobe parport_amiga > /lib/modules/2.4.0-test8/kernel/drivers/parport/parport_amiga.o: unresolved symbol iobarrier_rw Sorry, I should have tried to compile it. Should be fixed now. > (i updated only parport_amiga.c as i saw no other files where changed since > my last update 2 days ago, is it ok ?) Yes, that's ok, it's even enough here to do 'make modules SUBDIRS=drivers/parport'. bye, Roman |
|
From: Roman Z. <zi...@us...> - 2000-10-12 07:53:18
|
CVSROOT: /cvsroot/linux-apus Module name: 2.3 Repository: 2.3/drivers/parport/ Changes by: zi...@sl.... 00/10/12 00:53:17 Modified files: 2.3/drivers/parport/: parport_amiga.c Log message: include missing |
|
From: Robert R. <ro...@pl...> - 2000-10-12 07:15:46
|
> > > > Can you try the new version, I just commited? I recompiled only the modules (i had all that was related to parallel port as modules in my .config) and here is what i got: modprobe parport_amiga /lib/modules/2.4.0-test8/kernel/drivers/parport/parport_amiga.o: unresolved symbol iobarrier_rw /lib/modules/2.4.0-test8/kernel/drivers/parport/parport_amiga.o: insmod /lib/modules/2.4.0-test8/kernel/drivers/parport/parport_amiga.o failed /lib/modules/2.4.0-test8/kernel/drivers/parport/parport_amiga.o: insmod parport_amiga failed Just in case i'm recompiling whole kernel now. (i updated only parport_amiga.c as i saw no other files where changed since my last update 2 days ago, is it ok ?) -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
|
From: Robert R. <ro...@pl...> - 2000-10-11 22:31:27
|
On Wed, Oct 11, 2000 at 06:15:08PM +0200, Michel Dänzer wrote:
> Robert Ramiega wrote:
>
> > I also spotted that under some higher loads (like 7 or so) X tend to crash
> > with signal 7. What this implies ?
>
> All I can say is that it's a bus error. Could that be a kernel problem?
Most probably as this is the only thing that changed lately on my system.
I've seen higher loads than 7 on my Amiga and X survived this.
I never could understand what Bus error means. I've seen first on Intel
boxes a couple of years ago... This was the message given by Netscape when
it crashed. I don't think i've seen it before on Linux/PPC ("bus error"
messge or signal 7)
--
Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate
UIN: 13201047 | http://www.plukwa.net/ | the power of Source
|
|
From: Robert R. <ro...@pl...> - 2000-10-11 22:20:19
|
On Wed, Oct 11, 2000 at 07:27:17PM +0200, Roman Zippel wrote: > Hi, > > On Wed, 11 Oct 2000, Robert Ramiega wrote: > > > what about printing ? under test8 it's screwed badly. Text gets printed > > roughly ok but postscript or anything like that gets messy at random points > > Can you try the new version, I just commited? Sure thing. I'm updating parport_amiga.c right now. Compiling and testing will have to wait til tommorow as i already am compiling a few things. -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
|
From: Roman Z. <zi...@fh...> - 2000-10-11 17:32:15
|
Hi, On Wed, 11 Oct 2000, Robert Ramiega wrote: > what about printing ? under test8 it's screwed badly. Text gets printed > roughly ok but postscript or anything like that gets messy at random points Can you try the new version, I just commited? If that doesn't help, someone has to do some real debugging on it. :) bye, Roman |
|
From: Roman Z. <zi...@us...> - 2000-10-11 17:25:12
|
CVSROOT: /cvsroot/linux-apus Module name: 2.3 Repository: 2.3/drivers/parport/ Changes by: zi...@sl.... 00/10/11 10:25:11 Modified files: 2.3/drivers/parport/: parport_amiga.c Log message: adding io barriers |
|
From: Michel <dae...@st...> - 2000-10-11 16:21:11
|
Sven LUTHER wrote: > > > > > In the attachement You'll find small tgz with my XF86Config and 4 > > > > > Xfree.log (with some combination of BusID and UseFBDev) I hope that > > > > > helps. > > > > > > > > Interesting. Looks like it always crashes if you specify the bus ID. > > > > Otherwise, it gets further, but then crashes. Sven, could it be due to > > > > some of your PM3 changes? > > > > > > No this is not possible, all pm3 changes i did test for the the chip to > > > be a pm3, and i did nothing yet for fbdev use. > > > > The problem might be exactly there. If there is no PCI, you can't check > > the PCI info. I had originally tried to guard all PCI related stuff by the > > FBDevProbed boolean (maybe we should change that to HavePCI or > > something?), maybe you accidentally broke the logic with your PM3 changes? > > No i think not that i did anything like that, the only stuff i did is > duplicate the permedia2v case in switches and rename it permedia3 and do > some modification then. > > BTW, maybe the glint driver would need some restructuring, i thinkk. > Whatever happened to the discution about fbdev probing we had some month ago > with (don't remember exactly, but he was one of the big xfree guys.) I guess you mean Egbert Eich? Of course, if we'd get PCI working in 2.4 as well it would be best to skip the fbdev probing code altogether probably. > Will try to do a pm3 fbdev this weekend. Good luck, remember that this probably won't help you with this bug as it's only about PCI not being available. 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-11 16:15:15
|
Robert Ramiega wrote: > I also spotted that under some higher loads (like 7 or so) X tend to crash > with signal 7. What this implies ? All I can say is that it's a bus error. Could that be a kernel problem? 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-10-11 13:46:55
|
Hi! On Mon, Oct 09, 2000 at 07:32:19PM +0200, Roman Zippel wrote: > Hi, > > We solved that problem now (I forgot to include the mailing list in the > reply). The problem was that the hw clock was called too often in a short > period (this part was btw introduced in test7). > > > Frank Petzold reported on IRC that lp is broken in test7 (as well as scsi > > emulation). In self made test5 i couldn't even load modules (modprobe keeps > > saying that device is busy; admitedly it;s realy high possible that i screwed > > something with modules as i was adding them later) > > Hmm, according to the linux-kernel list we're not the only people that > have a problem with scsi emulation... :-) what about printing ? under test8 it's screwed badly. Text gets printed roughly ok but postscript or anything like that gets messy at random points (the best what i could achieve is half page ok and than some garbage <<like semigraphic chars>> than some part of printout then garbage <<it wasn't even complete>>) Can this be related to timing probs in some other (than time.c) part of kernel? I also spotted that under some higher loads (like 7 or so) X tend to crash with signal 7. What this implies ? -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
107 messages has been excluded from this view by a project administrator.
