linuxdc-dev — Developer discussion list

Re: [linuxdc-dev] hi

[Ben S. <sr...@cs...>]

Could someone give me a quick and dirty "here is how to compile the
checked out kernel code from cvs" howto? I can't wait to start working on
this.

ben

-- 
Ben Srour
sr...@cs...

On Wed, 6 Nov 2002, Adrian McMenamin wrote:

> On Wednesday 06 Nov 2002 7:03 pm, Lorant Toth wrote:
> > hello,
> >
> > I'm new to this list. So maybe that's a dumb question but I am curious. Did
> > anybody ever try compile and run Qt/Embedded and qtopia/opie on the DC?
> > Should work memory-wise, have no idea about the qt/e internals though
> > (maybe it works with an fb-device?). I don't know but I'd love to see a guy
> > with some nice applications. Although Opie might look childish and for PDAs
> > I guess there are a few interesting apps like Konquerer running as well.
> >
> > Regards
> >
> > - Lorant
> >
> Both Marcus Brown and I were able to build static (ie total bloat) versions of
> the Qt/E apps, but some things wouldn't build and nothing would build shared.
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>

Re: [linuxdc-dev] hi

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

On Wednesday 06 Nov 2002 7:03 pm, Lorant Toth wrote:
> hello,
>
> I'm new to this list. So maybe that's a dumb question but I am curious. Did
> anybody ever try compile and run Qt/Embedded and qtopia/opie on the DC?
> Should work memory-wise, have no idea about the qt/e internals though
> (maybe it works with an fb-device?). I don't know but I'd love to see a guy
> with some nice applications. Although Opie might look childish and for PDAs
> I guess there are a few interesting apps like Konquerer running as well.
>
> Regards
>
> - Lorant
>
Both Marcus Brown and I were able to build static (ie total bloat) versions of 
the Qt/E apps, but some things wouldn't build and nothing would build shared.

Re: [linuxdc-dev] hi

[M. R. B. <mr...@0x...>]

* Lorant Toth <Lor...@gm...> on Wed, Nov 06, 2002:

> Ok, that is the problem, I see ;)
>=20
> I guess that means there is not such a toolchain. Is the SH/4 anyway SH/3=
=20
> compliant or does it have a different instruction set?
> I guess you already know that there is no such toolchain as described but=
=20
> if you're not sure I could *try* looking ;)
>=20

Such a toolchain exists, but we're having a hell of a time getting it to do
what we want (building/running shared executables).  GCC 3.2 + binutils
2.13 are what we're currently working with.

M. R.

Re: [linuxdc-dev] hi

[Lorant T. <Lor...@gm...>]

Ok, that is the problem, I see ;)

I guess that means there is not such a toolchain. Is the SH/4 anyway SH/3 
compliant or does it have a different instruction set?
I guess you already know that there is no such toolchain as described but 
if you're not sure I could *try* looking ;)

- Lorant

At 13:08 06.11.2002 -0600, M. R. Brown wrote:
>* Lorant Toth <Lor...@gm...> on Wed, Nov 06, 2002:
>
> > hello,
> >
> > I'm new to this list. So maybe that's a dumb question but I am curious. 
> Did
> > anybody ever try compile and run Qt/Embedded and qtopia/opie on the DC?
> > Should work memory-wise, have no idea about the qt/e internals though
> > (maybe it works with an fb-device?). I don't know but I'd love to see a 
> guy
> > with some nice applications. Although Opie might look childish and for 
> PDAs
> > I guess there are a few interesting apps like Konquerer running as well.
> >
>
>Find us a toolchain that can build and run both shared executables and the
>C++ library, and we'll build Qt/E.
>
>M. R.

[linuxdc-dev] My status

[M. R. B. <mr...@0x...>]

Website isn't finished yet, I'm hoping to have it done by the weekend.
However, because I couldn't pay my cable bill for last month, I may not
have a connection to upload it with.  Just FYI in case I go offline within
the next day or so.

M. R.

Re: [linuxdc-dev] hi

[M. R. B. <mr...@0x...>]

* Lorant Toth <Lor...@gm...> on Wed, Nov 06, 2002:

> hello,
>=20
> I'm new to this list. So maybe that's a dumb question but I am curious. D=
id=20
> anybody ever try compile and run Qt/Embedded and qtopia/opie on the DC?=
=20
> Should work memory-wise, have no idea about the qt/e internals though=20
> (maybe it works with an fb-device?). I don't know but I'd love to see a g=
uy=20
> with some nice applications. Although Opie might look childish and for PD=
As=20
> I guess there are a few interesting apps like Konquerer running as well.
>=20

Find us a toolchain that can build and run both shared executables and the
C++ library, and we'll build Qt/E.

M. R.

[linuxdc-dev] hi

[Lorant T. <Lor...@gm...>]

hello,

I'm new to this list. So maybe that's a dumb question but I am curious. Did 
anybody ever try compile and run Qt/Embedded and qtopia/opie on the DC? 
Should work memory-wise, have no idea about the qt/e internals though 
(maybe it works with an fb-device?). I don't know but I'd love to see a guy 
with some nice applications. Although Opie might look childish and for PDAs 
I guess there are a few interesting apps like Konquerer running as well.

Regards

- Lorant

Re: [linuxdc-dev] Further Reading

[Mike B. <mik...@ho...>]

    I'm up for a discussion on rolling-your-own distro.  I'm one of the
folks in the process of doing just that.  It would be helpful for me to hear
how other folks are using the DC kernel and what their environment looks
like.
    I'm currently running a CD with dcload-ip on it along with an ISO
filesystem of debian tools.  I boot my kernel + sh_boot using dcload.  I've
linked /lib and /usr from the gdrom to my ramdisk.  I can boot, configure
the network and run various shells and tools.  Next item for me is to get
the puppy networked so I can telnet in and also NFS mount my other boxes.
    Thanks for the pointers on building from scratch.

-mike


----- Original Message -----
From: "Arthur Othieno" <art...@gm...>
To: "LOCKE, Jonathan -Syntegra UK" <Jon...@sy...>
Cc: <lin...@li...>
Sent: Tuesday, November 05, 2002 9:20 AM
Subject: Re: [linuxdc-dev] Further Reading


> Hello John,
>
> If, as you have stated, are interested in rolling your own distro, you
> might want to take a look at the Linux from Scratch project
> (http://www.linuxfromscratch.org/) where you'll find the resources
> (mainly documentation) that you might need to get going.
>
> TLDP also has some helpful documentation although I can not specify what
> exactly you might find useful for your purpose off the top of my head,
> but, the From-Power-up-to-Bash-Prompt HOWTO may provide a useful insight
> - it did for me some time back ;) And last but not least...
>
> I've noticed a number of people on this list and probably elsewhere are
> currently or planning to roll their own distros. I was thinking,
> wouldn't it be a good (or even better) idea if we as a community put all
> this effort and ideas together to roll a standard distribution for the
> DC? Possibly by building on top of and taking ideas from already
> existing ones (Debian, Gentoo, et al)? I'm not sure whether this topic
> has been touched on before, or maybe it hasn't? But I just want to know
> what you think of it, that's all :)
>
> And congratulations to everyone involved on the soon-to-be-fully-revived
> website (can't wait to see what it holds beneath):)
>
> Arthur
>
> LOCKE, Jonathan -Syntegra UK wrote:
>
> >
> >
> > Hi all,
> >
> > I'm currently looking at Bill Gatliff's 'Running linux on the Sega Dream
> > Cast' article and 'linux from scratch', with a view to building my own
> > distro.
> >
> > I'd like to be able to use ppp/tcpip to connect to my linux workstation
> > through the serial coders cable that I have made and run CPPvm/PVM on
> > the dream cast.
> >
> > Can anyone suggest any further reading that may be of help to me or has
> > anyone had experiences of building a similar distro?
> >
> > Thanks Jon.
> >
> >
> >
> >
> >
> >
> > ********************************************************************
> >
> > This email may contain information which is privileged or confidential.
> > If you are not the intended recipient of this email, please notify the
> > sender immediately and delete it without reading, copying, storing,
> > forwarding or disclosing its contents to any other person
> > Thank you
> >
> > Check us out at http://www.syntegra.com
> >
> > ********************************************************************
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>

Re: [linuxdc-dev] Further Reading

[Arthur O. <art...@gm...>]

Hello John,

If, as you have stated, are interested in rolling your own distro, you 
might want to take a look at the Linux from Scratch project 
(http://www.linuxfromscratch.org/) where you'll find the resources 
(mainly documentation) that you might need to get going.

TLDP also has some helpful documentation although I can not specify what 
exactly you might find useful for your purpose off the top of my head, 
but, the From-Power-up-to-Bash-Prompt HOWTO may provide a useful insight 
- it did for me some time back ;) And last but not least...

I've noticed a number of people on this list and probably elsewhere are 
currently or planning to roll their own distros. I was thinking, 
wouldn't it be a good (or even better) idea if we as a community put all 
this effort and ideas together to roll a standard distribution for the 
DC? Possibly by building on top of and taking ideas from already 
existing ones (Debian, Gentoo, et al)? I'm not sure whether this topic 
has been touched on before, or maybe it hasn't? But I just want to know 
what you think of it, that's all :)

And congratulations to everyone involved on the soon-to-be-fully-revived 
website (can't wait to see what it holds beneath):)

Arthur

LOCKE, Jonathan -Syntegra UK wrote:

> 
> 
> Hi all,
> 
> I'm currently looking at Bill Gatliff's 'Running linux on the Sega Dream 
> Cast' article and 'linux from scratch', with a view to building my own 
> distro.
> 
> I'd like to be able to use ppp/tcpip to connect to my linux workstation 
> through the serial coders cable that I have made and run CPPvm/PVM on 
> the dream cast.
> 
> Can anyone suggest any further reading that may be of help to me or has 
> anyone had experiences of building a similar distro?
> 
> Thanks Jon.
> 
>  
> 
> 
> 
> 
> ********************************************************************
> 
> This email may contain information which is privileged or confidential. 
> If you are not the intended recipient of this email, please notify the 
> sender immediately and delete it without reading, copying, storing, 
> forwarding or disclosing its contents to any other person
> Thank you
> 
> Check us out at http://www.syntegra.com
> 
> ********************************************************************

[linuxdc-dev] Further Reading

[LOCKE, J. -S. U. <Jon...@sy...>]

> Hi all,
> 
> I'm currently looking at Bill Gatliff's 'Running linux on the Sega Dream
> Cast' article and 'linux from scratch', with a view to building my own
> distro. 
> 
> I'd like to be able to use ppp/tcpip to connect to my linux workstation
> through the serial coders cable that I have made and run CPPvm/PVM on the
> dream cast.
> 
> Can anyone suggest any further reading that may be of help to me or has
> anyone had experiences of building a similar distro?
> 
> Thanks Jon.
> 
>  
> 
> 


********************************************************************

This email may contain information which is privileged or confidential. If you are not the intended recipient of this email, please notify the sender immediately and delete it without reading, copying, storing, forwarding or disclosing its contents to any other person
Thank you

Check us out at http://www.syntegra.com

********************************************************************

Re: [linuxdc-dev] Building my own DC distro

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

Hi!  
  
> 2)  I'm not sure how to leave myself with a busybox shell using inittab  
Some time ago, I've got the same problem. My inittab looks like this:  
  
-------------------------------8<---------------------------------------------------------  
  
# Stuff on boot  
::sysinit:/etc/init.d/rc.sysinit  
  
# Stuff to run once  
::once:/etc/init.d/rcS  
  
# Start an "askfirst" shell on the console (whatever that may be)  
::askfirst:-/bin/sh  
  
# Stuff to do before rebooting  
::ctrlaltdel:/sbin/reboot  
  
-------------------------------8<---------------------------------------------------------  
  
My /etc/init.d/rcS, where I'm starting some essential services, looks like :  
  
-------------------------------8<---------------------------------------------------------  
#!/bin/sh  
  
echo "Mounting /proc filesystem..."  
mount -t proc none /proc  
  
sleep 1  
  
echo "Configuring lo..."  
/sbin/ifconfig lo 127.0.0.1 up  
  
echo "Starting slattach..."  
/sbin/slattach /dev/ttySC1  
  
sleep 1  
  
echo "Configuring sl0..."  
/sbin/ifconfig sl0 192.168.200.92 pointopoint 192.168.200.91 up  
  
# 192.168.200.92 is my Dreamcast  
# 192.168.200.91 is my computer, both attached through   
# the coders cable  
  
sleep 1  
  
echo "Starting utelnetd..."  
/usr/sbin/utelnetd -d  
  
sleep 1  
  
echo "Everything's done..."  
-------------------------------8<---------------------------------------------------------  
  
Hope, I could help you,  
  
        Chris  
  

Re: [linuxdc-dev] Building my own DC distro

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

On Monday 04 Nov 2002 7:29 pm, Mike Barnett wrote:
>     I'm building my own distro from scratch using a base of Gatliff's set
> up.  I'm up to date and able to build the kernel, busybox etc.  I'm a
> novice when it comes to the Linux boot process so forgive me if my
> questions are basic.
>
>     I'm stuck at two places currently:
> 1)  /dev/gdrom isn't showing up in the /dev directory
> 2)  I'm not sure how to leave myself with a busybox shell using inittab
>
>
> #1 - I'm using fsdev to populate the /dev directory, with the exception
> being /dev/console.  There's a bunch of devices shown in /dev, but not
> /dev/gdrom.  The gdrom driver is clearly being initialized and I traced it
> into the kernel and found that it is indeed being registered.  When I look
> at /proc/devices I can see that the gdrom is a block device with major of
> 250 (correct).  So why isn't /dev/gdrom appearing?  I can manually do a
> mknod and create it, mount it, etc.


I just assume that devfs doesn't know about gdroms - probably because the 
gdrom code doesn't properly handle initialisation under devfs. I'd have to 
look at the code.

Does that make sense?

Adrian

[linuxdc-dev] Building my own DC distro

[Mike B. <mik...@ho...>]

    I'm building my own distro from scratch using a base of Gatliff's =
set up.  I'm up to date and able to build the kernel, busybox etc.  I'm =
a novice when it comes to the Linux boot process so forgive me if my =
questions are basic.

    I'm stuck at two places currently:
1)  /dev/gdrom isn't showing up in the /dev directory
2)  I'm not sure how to leave myself with a busybox shell using inittab


#1 - I'm using fsdev to populate the /dev directory, with the exception =
being /dev/console.  There's a bunch of devices shown in /dev, but not =
/dev/gdrom.  The gdrom driver is clearly being initialized and I traced =
it into the kernel and found that it is indeed being registered.  When I =
look at /proc/devices I can see that the gdrom is a block device with =
major of 250 (correct).  So why isn't /dev/gdrom appearing?  I can =
manually do a mknod and create it, mount it, etc.

#2 - If I don't use an inittab, then the system boots up into a busybox =
shell.  Just press enter and I'm given a shell prompt.  But, /proc and =
my gdrom devices are not mounted.  I thought perhaps using inittab to =
run a script to do a mount -a would cause /proc and /gdrom to be =
mounted.  When I put an inttab in place, I don't know how to leave =
myself a shell running after the init is finished.  What's a good init =
line to put in inittab to cause this to happen?  I've looked at examples =
but can't find an example using busybox with the /dev/console.

Thanks
Mike

[linuxdc-dev] Fwd: [linuxdc-cvs] CVS: linux-sh-dc/drivers/mtd/maps vmu-flash.c,1.11,1.11.2.1

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

This code doesn't work properly with multiple vmus attached. They are all 
reported as being attached to the same port at the same position.

There is a crinkle in the vmu mtd code in that it assumes all vmus are the 
same (in reality they are, in theory they don't have to be) - but that means 
that they are all sharing the one mtd_info: hence they all report the same 
location.

----------  Forwarded Message  ----------

Subject: [linuxdc-cvs] CVS: linux-sh-dc/drivers/mtd/maps 
vmu-flash.c,1.11,1.11.2.1
Date: Sun, 03 Nov 2002 06:23:16 -0800
From: "M. R. Brown" <mr...@us...>
To: lin...@li...

Update of /cvsroot/linuxdc/linux-sh-dc/drivers/mtd/maps
In directory usw-pr-cvs1:/tmp/cvs-serv25520/drivers/mtd/maps

Modified Files:
      Tag: linux-sh-dc-2_4-branch
	vmu-flash.c
Log Message:
Add port/unit info to mtd_info->name

Index: vmu-flash.c
===================================================================
RCS file: /cvsroot/linuxdc/linux-sh-dc/drivers/mtd/maps/vmu-flash.c,v
retrieving revision 1.11
retrieving revision 1.11.2.1
diff -u -d -r1.11 -r1.11.2.1
--- vmu-flash.c	11 Sep 2002 20:09:07 -0000	1.11
+++ vmu-flash.c	3 Nov 2002 14:23:14 -0000	1.11.2.1
@@ -25,7 +25,8 @@

 static int VMU_BLOCK_SIZE;

-#define _DEBUG_
+/* Define this to get debugging messages */
+/* #define _DEBUG_ */

 #ifdef _DEBUG_
 #define DEBGM(fmt, args...)  (printk(KERN_INFO fmt, ##args))
@@ -37,7 +38,7 @@

 /* MTD Information */
 static struct mtd_info *vmu_flash_mtd = NULL;
-
+static unsigned char mtdname[40];

 static struct mapleq *lastmq;
 static struct maple_driver dc_flashmap_driver;
@@ -557,6 +558,7 @@

 static int dc_flashmap_connect(struct maple_driver_data *d)
 {
+
 	DEBGM
 	    ("Registering VMU Flash mapping and loading VMU Flash driver\n");

@@ -595,7 +597,6 @@
 	unsigned long basic_flash_data =
 	    be32_to_cpu(((unsigned long *) (lastmq->recvbuf))[1 + bit_cnt -
 							      controller_here]);
-
 	/* Create a permanent record
 	 * With thanks to Marcus Comstedt */

@@ -631,7 +632,6 @@
 		return -1;
 	}

-
 	do {
 		interruptible_sleep_on_timeout(&wq_mq, 1);
 	} while (lastmq == NULL);
@@ -648,7 +648,8 @@

 	/* Populate a mtd_info */
 	vmu_flash_mtd = kmalloc(512, GFP_KERNEL);
-	vmu_flash_mtd->name = "Dreamcast VMU Flash";
+	sprintf(mtdname, "Dreamcast VMU Flash @ %c%c", ('A' + mqu->port), ('0' +
 mqu->unit)); +	vmu_flash_mtd->name = mtdname;

 	/* This is 'other' */
 	vmu_flash_mtd->type = MTD_OTHER;



-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
linuxdc-cvs mailing list
lin...@li...
https://lists.sourceforge.net/lists/listinfo/linuxdc-cvs

-------------------------------------------------------

Re: [linuxdc-dev] Internal flash support

[M. R. B. <mr...@0x...>]

* M. R. Brown <mr...@0x...> on Sun, Nov 03, 2002:

>=20
> After you've done this, you can read (and potentially write, but I haven't
> tested it and you're advised to tread carefully) flash to your heart's
> content.  Note that partition 0 "System configuration" is read-only in
> hardware.
>=20

Writes work fine.  I plan on writing a userspace library in the near future
that allows you to write data compatible with SEGA's utilities, so that any
game data stored in flash (is Blue Stinger the only one?) won't have to be
obliterated.

M. R.

[linuxdc-dev] Internal flash support

[M. R. B. <mr...@0x...>]

Is now in CVS.  To enable it, select the following under the "Memory
Technology Devices (MTD)" menu:

- Memory Technology Device (MTD) support
- MTD partitioning support
- Direct char device access to MTD devices=20

RAM/ROM/Flash chip drivers:
- Detect non-CFI AMD/JEDEC-compatible flash chips
- Support for AMD/Fujitsu flash chips

Mapping drivers for chip access:
- SEGA Dreamcast internal JEDEC-compatible flash device
[Note: you do not want to select "Disable SEGAs logical partition mapping"]

To play with it, after your system has booted, "cat /proc/mtd" to get a
list of partitions and the MTD devices that they are mapped to.  If you've
compiled in DevFS support, you're good to go, or else you may need to
create the /dev/mtd[0-7] devices by hand.  Do a "man mknod" and read
linux/Documentation/devices.txt to figure out how to do this.

After you've done this, you can read (and potentially write, but I haven't
tested it and you're advised to tread carefully) flash to your heart's
content.  Note that partition 0 "System configuration" is read-only in
hardware.

To the gentleman who owns a Development station, please send me a private
e-mail, as I'm curious as to whether or not flash is mapped differently or
is bigger on your machine.

M. R.

[linuxdc-dev] Re: Changes to vmufs

[M. R. B. <mr...@0x...>]

* Adrian McMenamin <ad...@mc...> on Sun, Nov 03, 2002:

> As the CVS list is not sending me copies of Paul's updates, I have had a =
look=20
> "by hand". AFAICS the changes are all correcting the inanities of my codi=
ng=20
> "style" rather than any substantive changes in algorithim. Is that right?
>=20

No, there were quite a few memory leaks and latent bugs that Paul cleaned
up...

> Has anybody used this? Care to comment?
>=20

=2E.. which I can attest to because I tested each fix as he committed it.
So far mounting and directory listing works, I've also read a couple of
files but I can't yet verify their contents.  However if you umount and
mount again the directory listing becomes a bit garbled.

> And what did I do wrong when I loaded it in to the cvs (as I can see that=
 the=20
> branch has been changed in some way, but I cannot follow how/why).
>=20

Besides renaming your two source files, Paul also merged and deleted
revisions every now and again.  You should be able to do a "cvs diff" to
compare each revision or a range of revisions.

M. R.

[linuxdc-dev] Changes to vmufs

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

As the CVS list is not sending me copies of Paul's updates, I have had a look 
"by hand". AFAICS the changes are all correcting the inanities of my coding 
"style" rather than any substantive changes in algorithim. Is that right?

Has anybody used this? Care to comment?

And what did I do wrong when I loaded it in to the cvs (as I can see that the 
branch has been changed in some way, but I cannot follow how/why).

Thanks

Adrian

[linuxdc-dev] VMU File system

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

Initial code for the vmu file system driver I have been working on is now in 
the CVS. There is no makefile as yet - you'll have to build that yourself.

The code seems to operate reasonably well as a read only file system driver - 
but there is lots more to do, including:

*	Writing code that it properly traverses FAT and not justa ssumes files are 
saved in reverse sequence
*	Properly saving VMU parameters and not just assuming all VMUs are the same

But the code as posted should allow you to ls, cat and cp most/all files on 
your VMU.

Tidying up will begin tomorrow.

Adrian

Re: [linuxdc-dev] File system question

[David W. <dav...@ia...>]

> > My question is: what is 's'? I assume it is socket file - I am not sure w=
> hy=20
> > the output has changed this way, but it would be good to know just what I=
>  am=20
> > doing wrong!
> 
> 's' does indeed indicate a socket, or a device. Can't remember which,
> sorry, but I'm pretty sure it's a socket, or mutex.

's' is the 'sticky' bit.  It has various uses depending on which position
it appears in.  If it's in the owner permissions, it's a SUID program--that
means that, when run, it gets run with the UID (user ID) of the owner of
the file.  A similar effect holds for the group ID--GID.

A 'man ls' will probably tell more and in a more comprehensable fashon.

Cheers,
David

Re: [linuxdc-dev] Linux Programming

[ePAc <ep...@ko...>]

I have to ass something here.. The Katana dev kit (the scsi device that
SEGA gave (ahem) to (*registered*) developers to create DC software
doesn't work quite the same as the real dreamcast. I do not know for sure
what the differences are, but I have seen people developed on those, and
unfortunatly, they don't boot anything but GDRom, but run software from
the PC host. so you might be able to load the kernel directly, but unless
you can find blank GDROMs, then you are probably not going to go real far
without a real DC.

I worked on Evil Dead, and the DC version was developed by a guy sitting
accross my cube at the time...

ePAc

On Fri, 1 Nov 2002, Jason Dodson wrote:

> Date: Fri, 1 Nov 2002 20:55:20 -0500
> From: Jason Dodson <min...@ya...>
> To: lin...@li...
> Subject: Re: [linuxdc-dev] Linux Programming
>
> Neither. Just now that I have this dev kit, I have more... interest in
> playing with the dreamcast is all.
>
> Jason
>
> ----- Original Message -----
> From: <ps...@wi...>
> To: <lin...@li...>
> Sent: Friday, November 01, 2002 3:28 PM
> Subject: Re: [linuxdc-dev] Linux Programming
>
>
> > What do you intend to do with the katana dev machine? Or, that is to say,
> what does it offer that a standard dreamcast does not? Hard-drive space and
> easier booting?
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by: See the NEW Palm
> > Tungsten T handheld. Power & Color in a compact size!
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> > _______________________________________________
> > Linuxdc-dev mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
>

---
Nothing is foolproof to a sufficiently talented fool...
  oo
,(..)\
  ~~

Re: [linuxdc-dev] File system question

[Daniel S. <ds...@tr...>]

On Sat, Nov 02, 2002 at 12:24:27PM +0000, Adrian McMenamin scrawled:
> Changing the code on the vmufs driver last night I started toi get output=
 like=20
> this from an ls command:
>=20
>=20
> srwx
>=20
>=20
> My question is: what is 's'? I assume it is socket file - I am not sure w=
hy=20
> the output has changed this way, but it would be good to know just what I=
 am=20
> doing wrong!

's' does indeed indicate a socket, or a device. Can't remember which,
sorry, but I'm pretty sure it's a socket, or mutex.

--=20
Daniel Stone                                     <dstone@trinity.unimelb.ed=
u.au>
Developer, Trinity College, University of Melbourne

[linuxdc-dev] File system question

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

Changing the code on the vmufs driver last night I started toi get output like 
this from an ls command:


srwx


My question is: what is 's'? I assume it is socket file - I am not sure why 
the output has changed this way, but it would be good to know just what I am 
doing wrong!


Adrian

Re: [linuxdc-dev] Linux Programming

[Jason D. <min...@ya...>]

Neither. Just now that I have this dev kit, I have more... interest in
playing with the dreamcast is all.

Jason

----- Original Message -----
From: <ps...@wi...>
To: <lin...@li...>
Sent: Friday, November 01, 2002 3:28 PM
Subject: Re: [linuxdc-dev] Linux Programming


> What do you intend to do with the katana dev machine? Or, that is to say,
what does it offer that a standard dreamcast does not? Hard-drive space and
easier booting?
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxdc-dev

Re: [linuxdc-dev] Linux Programming

[Jason D. <min...@ya...>]

I got one at Electronics Boutique for $10. Though Im sure
http://www.lik-sang.com would be a good place to look.

Jason

----- Original Message -----
From: "Ben Srour" <sr...@cs...>
To: "Jason Dodson" <min...@ya...>
Cc: <lin...@li...>
Sent: Friday, November 01, 2002 3:28 PM
Subject: Re: [linuxdc-dev] Linux Programming


> I'm basically also just getting started with doing LinuxDC development.
> I've spent more of my time doing KOS programming.
>
> How much do you really need a keyboard and if so where do you suggest
> getting one? (cheap)
>
> Ben
>
> --
> Ben Srour
> sr...@cs...
>
> On Fri, 1 Nov 2002, Jason Dodson wrote:
>
> > Thanks... youre my hero.
> >
> >
> > ----- Original Message -----
> > From: "M. R. Brown" <mr...@0x...>
> > To: "Jason Dodson" <min...@ya...>
> > Cc: <lin...@li...>
> > Sent: Friday, November 01, 2002 2:58 PM
> > Subject: Re: [linuxdc-dev] Linux Programming
> >
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by: See the NEW Palm
> > Tungsten T handheld. Power & Color in a compact size!
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> > _______________________________________________
> > Linuxdc-dev mailing list
> > Lin...@li...
> > https://lists.sourceforge.net/lists/listinfo/linuxdc-dev
> >