linuxdc-dev — Developer discussion list

[linuxdc-dev] Re: [linuxsh-dev] Maple DMA

[Alex B. <ker...@be...>]

On Sun, 2004-06-20 at 19:15, Adrian McMenamin wrote:
> 	for (i=0; i<(1<<MAPLE_DMA_PAGES); i++)
> 			dma_cache_wback_inv(maple_sendbuf+i*PAGE_SIZE, PAGE_SIZE);
> 		
> 
> Could someone fill me in?

It invalidates the cache lines for the buffer you are DMA'ing so if you
read or write a value to the buffer post DMA it forces the processor to
pick up the value from memory instead of using the internal cache.

Otherwise weirdness can ensue...

-- 
Alex, Kernel Hacker: http://www.bennee.com/~alex/

Hackers are just a migratory lifeform with a tropism for computers.

[linuxdc-dev] Maple DMA

[Adrian M. <ad...@mc...>]

I am working on a rewrite of the Maple code in the Linux SH repository.

I want the maple bus to query port on start up to determine which devices=
 are=20
initally attached. So I am building the various MAPLE_COMMAND_DEVINFO buf=
fers=20
to send. Going along slowly, learning as I do it...

But I am wondering what the code below (in the existing driver) does as I=
 have=20
to say my knowledge of DMA is shady


=09for (i=3D0; i<(1<<MAPLE_DMA_PAGES); i++)
=09=09=09dma_cache_wback_inv(maple_sendbuf+i*PAGE_SIZE, PAGE_SIZE);
=09=09

Could someone fill me in?

Thanks

Adrian

Re: [linuxdc-dev] [PATCHES] Started work on maple driver

[Paul M. <le...@li...>]

On Thu, Jun 17, 2004 at 12:05:09AM +0100, Adrian McMenamin wrote:
> This is pretty crude stuff and doesn't even work properly in the limited =
way=20
> it is impolemented so far, but here it is for your perusal. (NB: these ar=
e=20
> against the maple code in the linuxsh repository).
>=20
For starters, please do all of the sysfs registration and handling in a new
maple-sysfs.c, it's ok to have one or two ifdefs in maple.c to hook into it,
but it would be preferrable to keep it isolated since sysfs is now under
CONFIG_SYSFS, so we may not always want it. If you look at the dma code, it
does similar things (though not as a bus), so you may want to look at that.
Additionally, you may also want to look at arch/sh/kernel/cpu/bus.c which
implements SH-bus as a dummy bus to handle registration of things that have
nowhere better to go (or things that could be done as platform device, but
have additional requirements, etc.). Ideally, maple will have a similar
registration method from a driver point of view.

> @@ -1,7 +1,20 @@
>  /*
> + *=09
>   *	Maple Bus device driver
>   */
> =20
> +/*************************
> + * Maple Bus Driver for  *
> + * SEGA Dreamcast 	 *
> + * Copyright Paul Mundt  *
> + * 2000 - 2004           *
> + * Sections copyright    *
> + * Adrian McMenamin      *
> + * 2004                  *
> + * Licensed under	 *
> + * version 2 of the GPL  *
> + *************************/
> +
>  #include <linux/config.h>
>  #include <linux/kernel.h>
>  #include <linux/module.h>

I didn't write this, so you can drop my name entirely. I'm not sure who the
original author of this is, it's had a bunch of different people hacking on=
 it
at some point or another though.

> @@ -65,7 +97,7 @@
>  	struct list_head *lh =3D (void *)driver;
>  	list_add(lh, &maple_driver_list);
> =20
> -	MOD_INC_USE_COUNT;
> +	/* MOD_INC_USE_COUNT; Redundant under 2.6 module code */
> =20
>  	pr_info("maple: registered driver: %s (function 0x%lx)\n",
>  	       driver->name, driver->function);
> @@ -77,7 +109,7 @@
>  	struct list_head *lh =3D (void *)driver;
>  	list_del(lh);
> =20
> -	MOD_DEC_USE_COUNT;
> +	/* MOD_DEC_USE_COUNT; */
> =20
>  	pr_info("maple: unregistered driver: %s (function 0x%lx)\n",
>  	       driver->name, driver->function);

It's probably worth adding an owner to the maple dev struct and doing
__module_get()/__module_put() on that for proper refcounting.

Other then that, it looks like a decent start, though much of maple.c needs
to be rewritten regardless due to its current inability to handle subdevice=
s,
general cruftiness of the list management, etc. another good reason to keep
the sysfs stuff abstracted in maple-sysfs.c, then we can rewrite maple.c
without stepping over any of the sysfs code.

[linuxdc-dev] [PATCHES] Started work on maple driver

[Adrian M. <ad...@mc...>]

This is pretty crude stuff and doesn't even work properly in the limited =
way=20
it is impolemented so far, but here it is for your perusal. (NB: these ar=
e=20
against the maple code in the linuxsh repository).

I have been working on rewriting the maple driver to match the driver mod=
el in=20
the 2.6 kernel. I've had trouble finding the time to do this properly, so=
 the=20
results are very limited - but this will give you entries of a sort in sy=
sfs=20
if nothing else :)

Apologies for the stray bits of code loitering here too.

More to follow in the next few days


Adrian

--- maple.c=092004-06-16 23:52:30.000000000 +0100
+++ tmpspace/linux-2.6.6/drivers/maple/maple.c=092004-06-16 23:54:04.0000=
00000=20
+0100
@@ -1,7 +1,20 @@
 /*
+ *=09
  *=09Maple Bus device driver
  */
=20
+/*************************
+ * Maple Bus Driver for  *
+ * SEGA Dreamcast =09 *
+ * Copyright Paul Mundt  *
+ * 2000 - 2004           *
+ * Sections copyright    *
+ * Adrian McMenamin      *
+ * 2004                  *
+ * Licensed under=09 *
+ * version 2 of the GPL  *
+ *************************/
+
 #include <linux/config.h>
 #include <linux/kernel.h>
 #include <linux/module.h>
@@ -13,6 +26,7 @@
 #include <linux/string.h>
 #include <linux/completion.h>
 #include <linux/interrupt.h>
+#include <linux/device.h>
=20
 #include <asm/page.h>
 #include <asm/io.h>
@@ -36,15 +50,33 @@
 static DECLARE_COMPLETION(kmapled_exited);
 static int kmapled_pid =3D 0;
=20
+
 struct timer_list maple_timer;
=20
 unsigned long *maple_sendbuf, *maple_sendptr, *maple_lastptr;
 unsigned long maple_pnp_time;
=20
+static int maple_bus_match(struct device * dev, struct device_driver * d=
rv)=20
+{
+=09pr_info("MAPLE: maple_bus_match called automagically\n");
+=09return 0;
+}
+
+
+/* Work with new driver structures for 2.6 */
+struct bus_type maple_bus_type =3D {
+       .name=09=3D "maple",
+       .match=09=3D maple_bus_match,
+};
+
+
+
+
 static struct maple_driver maple_dummy_driver =3D {
 =09.name=09=09=3D "Dummy",
 };
=20
+
 static void maple_dump_devinfo(struct maple_devinfo *devinfo)
 {
 =09pr_debug("  function:     0x%08x\n", be32_to_cpu(devinfo->function));
@@ -65,7 +97,7 @@
 =09struct list_head *lh =3D (void *)driver;
 =09list_add(lh, &maple_driver_list);
=20
-=09MOD_INC_USE_COUNT;
+=09/* MOD_INC_USE_COUNT; Redundant under 2.6 module code */
=20
 =09pr_info("maple: registered driver: %s (function 0x%lx)\n",
 =09       driver->name, driver->function);
@@ -77,7 +109,7 @@
 =09struct list_head *lh =3D (void *)driver;
 =09list_del(lh);
=20
-=09MOD_DEC_USE_COUNT;
+=09/* MOD_DEC_USE_COUNT; */
=20
 =09pr_info("maple: unregistered driver: %s (function 0x%lx)\n",
 =09       driver->name, driver->function);
@@ -120,6 +152,9 @@
 =09=09kfree(dev);
 =09=09return NULL;
 =09}
+=09/* Setup kernel device */
+=09dev->sys_maple_dev.bus =3D &maple_bus_type;
+
=20
 =09return dev;
 }
@@ -139,6 +174,7 @@
 {
 =09struct list_head *lh =3D (void *)dev;
 =09list_add_tail(lh, &maple_dev_list);
+=09
 }
=20
=20
@@ -227,6 +263,7 @@
=20
 =09pr_info("maple(%d,%d): Connected(function 0x%lx)\n",
 =09       dev->port, dev->unit, function);
+=09
=20
 =09list_for_each(lh, &maple_driver_list) {
 =09=09driver =3D (struct maple_driver *)lh;
@@ -244,6 +281,18 @@
 =09=09maple_dump_devinfo(&dev->devinfo);
 =09=09dev->driver =3D &maple_dummy_driver;
 =09}
+=09
+
+=09/* Add this device to the sysfs list */
+=09list_add_tail(&dev->sys_maple_dev.bus_list, &maple_bus_type.devices.l=
ist);
+=09sprintf(dev->sys_maple_dev.bus_id, "maple:%d:%d.0x%lx\n", dev->port,=20
dev->unit, function);
+=09sprintf(dev->sys_maple_dev.kobj.name, dev->product_name);
+=09dev->sys_maple_dev.bus =3D &maple_bus_type;
+=09device_register(&dev->sys_maple_dev);
+=09pr_info("MAPLE: device registered\n");
+
+
+
=20
 }
=20
@@ -456,6 +505,12 @@
=20
 =09pr_info("SEGA Dreamcast MAPLE Bus drivers\n");
=20
+=09/* Register with sysfs */
+       =09if (bus_register(&maple_bus_type) !=3D 0)
+=09=09goto cleanup;
+=09pr_info("Maple bus registered\n");
+=20
+
 =09/* Allocate DMA buffer */
 =09maple_sendbuf =3D (void *)__get_dma_pages(GFP_KERNEL, MAPLE_DMA_PAGES=
);
 =09if (maple_sendbuf =3D=3D NULL)
@@ -481,10 +536,10 @@
=20
 =09/* Start to scan ports */
 =09maple_pnp_time =3D 0;
-
-        /* Initialize hardware */
+=09
+=09/* Initialize hardware */
         ctrl_outl(MAPLE_MAGIC, MAPLE_RESET);
-        ctrl_outl(0, MAPLE_RESET2);
+=09ctrl_outl(0, MAPLE_RESET2);
         ctrl_outl(MAPLE_2MBPS|MAPLE_TIMEOUT(50000), MAPLE_SPEED);
 =09ctrl_outl(PHYSADDR(maple_sendbuf), MAPLE_DMAADDR);
         ctrl_outl(1, MAPLE_ENABLE);
@@ -494,7 +549,6 @@
         maple_timer.expires =3D jiffies + MAPLE_SCANHZ;
         maple_timer.function =3D maple_timer_handler;
         add_timer(&maple_timer);
-
         return 0;
=20
  cleanup:
@@ -526,6 +580,9 @@
 EXPORT_SYMBOL(maple_register_driver);
 EXPORT_SYMBOL(maple_unregister_driver);
 EXPORT_SYMBOL(maple_getcond_callback);
+EXPORT_SYMBOL(maple_bus_type);
+
+MODULE_LICENSE("GPL"); //avoid kernel tainting
=20
 /*
  * Local variables:





=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D

--- maple.h=092004-06-16 23:56:32.000000000 +0100
+++ tmpspace/linux-2.6.6/include/linux/maple.h=092004-06-16 22:47:26.0000=
00000=20
+0100
@@ -89,8 +89,10 @@
 };
=20
=20
+
 struct maple_device {
 =09struct list_head list;
+=09struct list_head sysfs_list;
 =09struct maple_driver *driver;
 =09struct mapleq *mq;
 =09void *private_data;
@@ -101,8 +103,17 @@
 =09unsigned char port, unit;
 =09char product_name[32];
 =09char product_license[64];
+=09
+=09/* 2.6.x kernel compliance */
+=09struct device sys_maple_dev;
+=09
 };
=20
+extern struct bus_type maple_bus_type;
+
+
+
+
=20
 struct maple_driver {
 =09struct list_head list;

[linuxdc-dev] Savve Up To 98% On Software Buying old

[Maragret M. <why...@sa...>]

expression sake shine manners identify sun 

[linuxdc-dev] Serial ports and the Dreamcast and Slackware Linux 9.1

[Gregg C L. <dr...@wo...>]

Hello from Gregg C Levine
Is anyone other then myself using Slackware Linux 9.1 for his host
development?

I can use the development tools that I grabbed from the LinuxSH site to
build what I want to test, and most of the time it works. However, it
refuses to be sent to the unit via the serial port. What special magic did
you need to do to get your system to talk to your unit? On the plus side I
can confirm that the DC serial upload tool works from Windows using a
precompiled Cygwin binary. I can send it the binaries that I built via my
Linux development suite.
Gregg C Levine drwho8 atsign worldnet dot att dot net
"Oh my!" The Second Doctor's nearly favorite phrase.

Re: [linuxdc-dev] IDE Hard Drive

[Mike F. <va...@ge...>]

On Tuesday 08 June 2004 01:57 pm, Quang Ngo wrote:
> It would be nice if you could tell us how you are doing with your project.
> Maybe set up a simple website?

i'll start posting it on linuxdc.sf.net when i get more info ... i'm trying to 
get a programmer for the xilinx XC95108 chips that *wont* cost me $800 :(
-mike

Re: [linuxdc-dev] Re: Maple Bus magic number etc

[Adrian M. <ad...@mc...>]

On Tuesday 08 June 2004 00:19, Paul Mundt wrote:
> On Mon, Jun 07, 2004 at 11:59:58PM +0100, Adrian McMenamin wrote:
> > Looking through the code for the driver I see this:
> >
> >         /* Initialize hardware */
> >         ctrl_outl(MAPLE_MAGIC, MAPLE_RESET);
> >         ctrl_outl(0, MAPLE_RESET2);
> >         ctrl_outl(MAPLE_2MBPS|MAPLE_TIMEOUT(50000), MAPLE_SPEED);
> > =09ctrl_outl(PHYSADDR(maple_sendbuf), MAPLE_DMAADDR);
> >         ctrl_outl(1, MAPLE_ENABLE);
> >
> > Is this documented anywhere? I cannot find anything on Marcus's site =
or
> > on google.
>
> No, it's not documented, that's precisely why it's a "magic" value.
>
> MAPLE_MAGIC is simply the "magic" value that needs to be written to
> MAPLE_RESET in order to reset the bus. I'm not aware of anyone having
> reverse engineered the maple stuff any further then what documentation =
is
> readily available, so it will remain a magic value until someone figure=
s
> out the register description.

Would you know what signals these generate on the bus? Which ones produce=
=20
interrupts etc? Wondering which one to trap to initialise the devices to =
meet=20
the new driver specs.

About to do a bit of hacking to find I suppose.

Adrian

[linuxdc-dev] IDE Hard Drive

[Kevin C. <kev...@co...>]

Hello,
    Does anyone know where I can find a good FAQ/How-To on how to =
'hook-up' and IDE Hard Drive to a Dreamcast. I have seen pictures, so I =
know it is possible... I just don't know how. OK, and now here is =
something I am almost sure is not possible, but I might as well ask... =
Is there a way to hook up, lets say a PCMCIA D-Link card (the only =
reason I say PCMCIA is because I have like 3, I can get my hands on =
another kind if it is possible), and use it as a Brodband Adapter? Any =
help you can give would be greatly appreciated, Thank You,

KEVIN

[linuxdc-dev] Re: Maple Bus magic number etc

[Paul M. <le...@li...>]

On Mon, Jun 07, 2004 at 11:59:58PM +0100, Adrian McMenamin wrote:
> Looking through the code for the driver I see this:
>=20
>         /* Initialize hardware */
>         ctrl_outl(MAPLE_MAGIC, MAPLE_RESET);
>         ctrl_outl(0, MAPLE_RESET2);
>         ctrl_outl(MAPLE_2MBPS|MAPLE_TIMEOUT(50000), MAPLE_SPEED);
> 	ctrl_outl(PHYSADDR(maple_sendbuf), MAPLE_DMAADDR);
>         ctrl_outl(1, MAPLE_ENABLE);
>=20
> Is this documented anywhere? I cannot find anything on Marcus's site or o=
n=20
> google.
>=20
No, it's not documented, that's precisely why it's a "magic" value.

MAPLE_MAGIC is simply the "magic" value that needs to be written to MAPLE_R=
ESET
in order to reset the bus. I'm not aware of anyone having reverse engineered
the maple stuff any further then what documentation is readily available, s=
o it
will remain a magic value until someone figures out the register descriptio=
n.

[linuxdc-dev] Maple Bus magic number etc

[Adrian M. <ad...@mc...>]

Looking through the code for the driver I see this:

        /* Initialize hardware */
        ctrl_outl(MAPLE_MAGIC, MAPLE_RESET);
        ctrl_outl(0, MAPLE_RESET2);
        ctrl_outl(MAPLE_2MBPS|MAPLE_TIMEOUT(50000), MAPLE_SPEED);
=09ctrl_outl(PHYSADDR(maple_sendbuf), MAPLE_DMAADDR);
        ctrl_outl(1, MAPLE_ENABLE);

Is this documented anywhere? I cannot find anything on Marcus's site or o=
n=20
google.

Thanks

Adrian

[linuxdc-dev] Maple dummy driver

[Adrian M. <ad...@mc...>]

What is the purpose of this?

Is it just a central "holder" - a marker for the Dreamcast itself on the =
bus,=20
or is it just a dummy device because you haven't written the code yet?

Adrian

Re: [linuxdc-dev] Mounting swap on nfs

[Mike F. <va...@ge...>]

On Friday 04 June 2004 06:58 pm, Paul Mundt wrote:
> You're better off just using mtdram or something and swapping to unmapped
> VRAM.

are there updated docs for how to do this with 2.6 ?  and/or could someone 
just tell me :)
i've only found vague references for 2.4 with my searching ...
-mike

Re: [linuxdc-dev] Mounting swap on nfs

[Paul M. <le...@li...>]

On Fri, Jun 04, 2004 at 02:32:23PM -0700, Tom Rini wrote:
> > For future reference, and with thanks to Paul - this is quite easy with=
 2.6=20
> > and a busy box setup configured to include losetup:
> >=20
> > dd if=3D/dev/zero of=3Dswap.img bs=3D1k count=3D16384 ; losetup /dev/lo=
op/0 swap.img ;=20
> > mkswap /dev/loop/0 ; swapon /dev/loop/0
> >=20
> > Haven't tested it at all thoroughly though, but it seems to be running =
fine.
>=20
> This is something you can do on 2.4.  But, AFAIK this can still fall
> down when memory pressure gets too bad.
>=20
Yes, swapping over NFS is error prone regardless. NBD is really the best way
to go (the patches for swapping over NFS are quite out of date), but swappi=
ng
to a loopback-bound swapfile over NFS still works in a pinch.

You're better off just using mtdram or something and swapping to unmapped
VRAM.

Re: [linuxdc-dev] Mounting swap on nfs

[Mike F. <va...@ge...>]

On Friday 04 June 2004 03:50 pm, Adrian McMenamin wrote:
> For future reference, and with thanks to Paul - this is quite easy with 2.6
> and a busy box setup configured to include losetup:
>
> dd if=/dev/zero of=swap.img bs=1k count=16384 ; losetup /dev/loop/0
> swap.img ; mkswap /dev/loop/0 ; swapon /dev/loop/0

yep ... ive gotten mixed results but i suspect it's not the fault of 
loopback ;)

ive also utilized nbd and that seemed to work well
-mike

Re: [linuxdc-dev] Mounting swap on nfs

[Tom R. <tr...@ke...>]

On Fri, Jun 04, 2004 at 08:50:37PM +0100, Adrian McMenamin wrote:

> For future reference, and with thanks to Paul - this is quite easy with 2.6 
> and a busy box setup configured to include losetup:
> 
> dd if=/dev/zero of=swap.img bs=1k count=16384 ; losetup /dev/loop/0 swap.img ; 
> mkswap /dev/loop/0 ; swapon /dev/loop/0
> 
> Haven't tested it at all thoroughly though, but it seems to be running fine.

This is something you can do on 2.4.  But, AFAIK this can still fall
down when memory pressure gets too bad.

-- 
Tom Rini
http://gate.crashing.org/~trini/

[linuxdc-dev] Mounting swap on nfs

[Adrian M. <ad...@mc...>]

For future reference, and with thanks to Paul - this is quite easy with 2=
=2E6=20
and a busy box setup configured to include losetup:

dd if=3D/dev/zero of=3Dswap.img bs=3D1k count=3D16384 ; losetup /dev/loop=
/0 swap.img ;=20
mkswap /dev/loop/0 ; swapon /dev/loop/0

Haven't tested it at all thoroughly though, but it seems to be running fi=
ne.

Adrian

[linuxdc-dev] Re: [linuxsh-dev] custom Dreamcast parallel port

[Paul M. <le...@li...>]

(CC list pruned.. this entire thread is barely on-topic as-is..)

On Fri, May 28, 2004 at 10:40:26PM +0100, Adrian McMenamin wrote:
> For a little while in 2002 I was perhaps the most active Dreamcast linux=
=20
> kernel hacker - writing a device driver or two and even a filesystem for =
the=20
> VMU device (though I was standing on the shoulders of giants). Change of =
job=20
> etc meant all that had to stop and there were a few others still going, b=
ut=20
> my assessment is that the DC hacking scence - both Linux and homebrew stu=
ff=20
> generally - has more or less died in the last six months.
>=20
The DC dev community has been dwindling for years, so this is nothing new.
However, it still remains a fairly accessible peice of hardware, relatively
well supported in LinuxSH, etc. so there will always be people idly hacking
on it (myself included). Further undocumented hardware and registers will
certainly keep it alive from a passive interest point of view. I'll certain=
ly
take a DC over a 7750 SolutionEngine any day.

In the 2.6 tree now the DC is still one of the best supported boards (mostly
on account of the fact that I did most of my development and testing on it),
and it should continue to be well supported in the future as well. If the
NetBSD effort is alive now, it would certainly be a good idea for someone to
keep an eye on that and see if they come up with anything interesting that
we don't support.

> A pity, but that's the way it goes - certainly no commercial support was =
ever=20
> likely and the prohibitive cost of the nic for the DC meant serious=20
> developers were always going to be thin on the ground.

Even given the cost of the BBA, it's still a very affordable and accessible
platform (especially when your other alternatives are costly reference boar=
ds).

Though in comparison to commercially viable solutions, most of the homewbrew
scene seems to have flocked to the PS2, etc.

Given the topic of drivers and such, this will all get done in time. With O=
SS
going away probably in 2.7, we don't really have much of a choice for ALSA
migration, so the AICA stuff will all be picked up and merged whenever that
happens. Maple needs to be rewritten entirely to support sub-devices, confo=
rm
with the new driver model, interoperate with the DMA API, etc. at which poi=
nt
we should finally be able to get the thing merged in mainline and never hav=
e to
touch it again, until someone decides they don't like the driver model and
decides to rewrite it again, etc.

None of this stuff is very high on my TODO list, so this obviously isn't go=
ing
to get done quickly, ideally someone else with an interest in this stuff sh=
ould
do this and just send patches (or better yet, use GNU arch so I can merge
things easier). LinuxDC still has some useful things in CVS, but it's quite
outdated, so resurrecting the linux-sh-dc stuff would probably be
a worthwhile first step (at least for 2.6, 2.4 is done at this point, so no
one should even be thinking about it).

[linuxdc-dev] Stupid Will Only Buy Softwares From Shop, lol thrombin

[Maegan M. <yp...@mb...>]

speller touches catadupe brotula bello 
villian monachal allign appraising 

[linuxdc-dev] SUPER DISCOUNT SOFTWARES FROM 30 - 100 BUCKS practically

[Delphia L. <yxd...@wo...>]

tea planning thursday also prairie moment reference horses etc weeks 
called effect seem paid quietly building blood master followed teach independent possible i 

[linuxdc-dev] y u stopped replying my mail?

[Chang C. <gpc...@wa...>]

reestate gatecrash hothouse allotropy ruralist giovane tarsier 
bankruptcy publicize throwster bountiful marland shunted parula laundress gavidae mindfully blur climber moppet 
brut cogency matronymic retrocede registrary granitic herbist fandango gloom 

[linuxdc-dev] ...Hi

[Kevin<COGECO> <kev...@co...>]

    OK, believe it or not, I am COMPLETELY new to this Dreamcast Linux. =
Not Linux, just Dreamcast Linux. However I have used Xbox Linux before. =
I was wondering where I could get maybe an .iso or .img of a "Ready To =
Burn" DC Linux Distro. I have read a bunch of readme's, but have yet to =
'decypher' most of the documents (WAY to technical). Any URL, or maybe =
FTP sites I could get a Linux DC distro (ready to burn) would be greatly =
appreciated :D!


Thank you in advance,
KEVIN

[linuxdc-dev] TEST

[NunO f. <nm...@ne...>]

[linuxdc-dev] VIP INVITE

[cee <THE...@HO...>]

TUESDAY 11TH NOVEMBER WE ARE HAVING AN EXCLUSIVE VIP PARTY @ EMBASSY, 29 OLD =
BURLINGHTON STREET LONDON W1.....AS YOU ALL KNOW THERE ARE A LOT OF FAMOUS =
POPSTARS IN TOWN WHO HAVE CONFIRMED RESERVATION FOR TOMORROW AND AS YOU ARE =
ON OUR MAILING LIST WE CAN OFFER YOU AN EXCLUSIVE GUESTLIST....SO CALL ME : =
CEE 070500 28456 OR ARBILINA 07958 425166 TO CONFIRM YOUR RESERVATION =
GUESTLIST IS FREE SO DONT WORRY.
PLEASE ARRIVE EARLY TO AVOID DISSAPOINTMENT.....
10PM TILL LATE
CEE 070500 28456  OR ARBILINA 07958 425 166  

[linuxdc-dev] [ANN] SEGA VMU LCD Display device driver

[Christian B. <c.b...@tu...>]

Hi Folks!

I've written a device driver for the device mentioned
above because I want to use my SEGA VMU LCD Display for
showing some essential system information for
my ADSL software router.

The driver can be found=20

(Source code)
http://www-public.tu-bs.de:8080/~y0018536/dc/src/mlcd-0_0_4.tar.bz2

Best regards,

        Christian