linuxdc-dev — Developer discussion list

Re: [linuxdc-dev] Re: [linuxsh-dev] Completion of LinuxDC merge into LinuxSH

[<p2...@mi...>]

Hi,

> * YAEGASHI Takeshi <t...@ke...> on Thu, May 24, 2001:
> 
> > 
> > This surprised me a bit, because I've paied little attention to
> > your project's status for a long time.  Now it seems much better
> > than my drivers. ;-> Great work.
> > 
> 
> Hehe, imagine my surprise when your code was finally released, and we had
> basically the same drivers!  All of your work is appreciated, and I understand
> the situation you were in before, and I'm glad you're able to hack on these
> drivers :).  Here's what's on LinuxDC's agenda in the next few weeks, for
> those of you out there who want to help out:
> 

Last weekend I tried the cvs snapshot of the DC Linux kernel on a dreamcast
with BBA. I downloaded the kernel via the serial port. I had to make some 
small changes to the pci_gaps code to get the BBA to work.

> - Finish rewriting Maple subsystem
> - Finish drivers for the vmu MTD flash and LCD fb
> - Finish AICA RTC stuff
> - GD-ROM support
> - MTD driver for DC's internal flash

Any pointers on this ? I have done some work on MTD drivers.

> - ALSA or OSS drivers for the AICA system

I was planning on looking into this RSN. I have experience with ARM programming
on both linux and eCos. I was thinking of running eCos on the AICA :)

Peter.

Re: [linuxdc-dev] Re: [linuxsh-dev] Completion of LinuxDC merge into LinuxSH

[M. R. B. <mr...@li...>]

* YAEGASHI Takeshi <t...@ke...> on Thu, May 24, 2001:

> 
> This surprised me a bit, because I've paied little attention to
> your project's status for a long time.  Now it seems much better
> than my drivers. ;-> Great work.
> 

Hehe, imagine my surprise when your code was finally released, and we had
basically the same drivers!  All of your work is appreciated, and I understand
the situation you were in before, and I'm glad you're able to hack on these
drivers :).  Here's what's on LinuxDC's agenda in the next few weeks, for
those of you out there who want to help out:

- Finish rewriting Maple subsystem
- Finish drivers for the vmu MTD flash and LCD fb
- Finish AICA RTC stuff
- GD-ROM support
- MTD driver for DC's internal flash
- ALSA or OSS drivers for the AICA system
- if necessary, External DMA, and other minor subsystems

> 
> You may know BERO has already had the GD-ROM driver ported from
> NetBSD:
> 
> 	http://www.geocities.co.jp/Playtown/2004/dcdev/linux/linux.html
> 
> I have another driver based on this, and a standalone Debian
> system can boot on my Dreamcast with the kernel powered by it.
> 

Wow! This is ... cool! :)  I'm glad we have a starting point for writing a
GD-ROM driver, would you mind sending me the driver you have as well?  Some
of the things I wanted to support in addition to the PIO stuff Marcus has
done are DMA reads and audio playing, which is why I've been hesitant just
using his "stock" GD-ROM code :).  This is a tremendous help, thanks!

> I'm now working on adding GD-ROM drive and ISO9660 supports to
> eCos+RedBoot/Dreamcast to make it serve as a bootloader, and
> planning to distribute CD-Rs at LinuxWorld Expo/Tokyo.
> 

That would also be great, we've been mostly using dcload for sending
kernels over the BBA, but once we get proper GD-ROM support added a decent
bootloader will be required.  I've played with RedBoot a little bit, but
haven't sat down to get kernels booting via TFTP, etc.  I would be
interested in helping you out with this, just let me know :).

For those of you out there who don't hack kernels but still want to help,
you can, by:

- testing the kernels, finding bugs, and reporting them
- helping with documentation where needed (it's needed *badly*, ATM)
- using the cross-tools to port your favorite app/library over (hehe, I've
  already done SDL, just need to accel. that damn frame buffer :)
- helping get binary images together for those who don't have the means to
  build everything from scratch
- doing whatever else you can think of :)

M. R.

[linuxdc-dev] Re: [linuxsh-dev] Completion of LinuxDC merge into LinuxSH

[YAEGASHI T. <t...@ke...>]

In the article <200...@ma...>,
"M. R. Brown" <mr...@li...> wrote:

> Hi all,
> 
> Sorry for it taking so long, but I've completed the merge of LinuxDC driver
> support into LinuxSH:
> 
> - The Maple Bus driver has been shuffled around a bit to:
>   a) make it more consistent with kernel driver placement (Maple is a
>      *subsystem*, not a single driver ;-),
>   b) facilitate it's (complete) rewrite by Paul Mundt and myself.  The new
>      Maple core will be able to support a wide range of DC peripherals,
>      including MTD storage and framebuffer support for VMUs.
> - Support for Dreamcast System ASIC hardware events.  This allows us to
>   map hardware events to virtual IRQs, so that drivers can respond to
>   events as they would a normal IRQ.  Examples of this include the vsync
>   interrupt for the framebuffer, the BBA IRQ, GD-ROM DMA/Command
>   completion, etc.
> - The generic dcfb framebuffer driver has been replaced with the pvr2
>   framebuffer, in hopes of providing a standard driver for all video cards
>   based on the PowerVR2 architecture.  Acceleration (DMA blitting, etc.)
>   and better video mode support are on its way for pvr2.
> 
> There is some RTC stuff that's currently missing, but that's being rewritten
> so that I can integrate it with the new RTC changes.
> 
> Now that the basic stuff's been merged, future DC driver development will
> be folded back into LinuxSH after testing, so you'll always be able to grab
> the latest development stuff from linuxdc.org.

This surprised me a bit, because I've paied little attention to
your project's status for a long time.  Now it seems much better
than my drivers. ;-> Great work.

Please go ahead with merging your works into LinuxSH's CVS.


> I'm currently finishing up gathering enough info to write a GD-ROM driver,
> hopefully I'll be able to begin work on it this weekend.

You may know BERO has already had the GD-ROM driver ported from
NetBSD:

	http://www.geocities.co.jp/Playtown/2004/dcdev/linux/linux.html

I have another driver based on this, and a standalone Debian
system can boot on my Dreamcast with the kernel powered by it.

I'm now working on adding GD-ROM drive and ISO9660 supports to
eCos+RedBoot/Dreamcast to make it serve as a bootloader, and
planning to distribute CD-Rs at LinuxWorld Expo/Tokyo.

--
YAEGASHI Takeshi <t...@ke...>

[linuxdc-dev] Completion of LinuxDC merge into LinuxSH

[M. R. B. <mr...@li...>]

Hi all,

Sorry for it taking so long, but I've completed the merge of LinuxDC driver
support into LinuxSH:

- The Maple Bus driver has been shuffled around a bit to:
  a) make it more consistent with kernel driver placement (Maple is a
     *subsystem*, not a single driver ;-),
  b) facilitate it's (complete) rewrite by Paul Mundt and myself.  The new
     Maple core will be able to support a wide range of DC peripherals,
     including MTD storage and framebuffer support for VMUs.
- Support for Dreamcast System ASIC hardware events.  This allows us to
  map hardware events to virtual IRQs, so that drivers can respond to
  events as they would a normal IRQ.  Examples of this include the vsync
  interrupt for the framebuffer, the BBA IRQ, GD-ROM DMA/Command
  completion, etc.
- The generic dcfb framebuffer driver has been replaced with the pvr2
  framebuffer, in hopes of providing a standard driver for all video cards
  based on the PowerVR2 architecture.  Acceleration (DMA blitting, etc.)
  and better video mode support are on its way for pvr2.

There is some RTC stuff that's currently missing, but that's being rewritten
so that I can integrate it with the new RTC changes.

Now that the basic stuff's been merged, future DC driver development will
be folded back into LinuxSH after testing, so you'll always be able to grab
the latest development stuff from linuxdc.org.

I'm currently finishing up gathering enough info to write a GD-ROM driver,
hopefully I'll be able to begin work on it this weekend.

Have fun!

M. R.

Re: [linuxdc-dev] Re: DC NFS root filesystem

[Andrew M. <amo...@st...>]

I tried out these settings, as well as M.R. Brown's additions from the 
mailing list, but they seemed to have no effect.

Karl Trygve Kalleberg wrote:

>mrbrown's init.d/rcS
>#!/bin/sh
># Remount root read-write
>mount -n -o remount,defaults /
>rm -f /etc/mtab~
>mount -f -o remount,defaults /
>mount -a
>
>/etc/fstab root entry:
>192.168.12.11:/home/mrbrown/dcdev/nfs/busybox /  nfs \
>defaults,errors=remount-ro 0 0
>
>
>Kind regards,
>
>Karl T
>

Re: [linuxdc-dev] Re: DC NFS root filesystem

[M. R. B. <mr...@li...>]

* Karl Trygve Kalleberg <ka...@pr...> on Wed, May 16, 2001:

> mrbrown's init.d/rcS
> #!/bin/sh
> # Remount root read-write
> mount -n -o remount,defaults /
> rm -f /etc/mtab~
> mount -f -o remount,defaults /
> mount -a
> 
> /etc/fstab root entry:
> 192.168.12.11:/home/mrbrown/dcdev/nfs/busybox /  nfs \
> defaults,errors=remount-ro 0 0
> 

The only thing I'd add to that is /etc/inittab:
::sysinit:/etc/init.d/rcS
::askfirst:/bin/sh

But if you're using a debian distro, that should all be taken care of for
you, those file above are from a busybox NFS mount.

M. R.

Re: [linuxdc-dev] Re: DC NFS root filesystem

[Karl T. K. <ka...@pr...>]

mrbrown's init.d/rcS
#!/bin/sh
# Remount root read-write
mount -n -o remount,defaults /
rm -f /etc/mtab~
mount -f -o remount,defaults /
mount -a

/etc/fstab root entry:
192.168.12.11:/home/mrbrown/dcdev/nfs/busybox /  nfs \
defaults,errors=remount-ro 0 0


Kind regards,

Karl T

[linuxdc-dev] Re: DC NFS root filesystem

[Karl T. K. <ka...@pr...>]

On Wed, May 16, 2001 at 04:15:09PM -0400, Andrew Molloy wrote:
> I mounted it from the server and I can write to it.  Also, since I'm not 
> very familiar with NFS, is no_root_squash appropriate for the 
> Dreamcast?  I assumed so from the man page but it wasn't a very good 
> explanation.

no_root_squash is required if the client should be able to read files
private to root on the host machine. Then mounting root over NFS, you have
to specify no_root_squash. 

The theory from #linuxdc is that the init script that's supposed to
remount / read-write is screwed up. I've not toyed around with the root
image you mentioned myself, so my only advice is to look closely at the
boot script(s) and find out where it's supposed to remount root, then see
to it that the script actually does that.
 
> I've tried to connect to IRC, but I'm firewalled and the proxies don't 
> allow it.

That's a shame. If you have a squid proxy between you and the outer world,
there's a little neat trick called tcp-over-squid which should work.


Karl T

[linuxdc-dev] Re: DC NFS root filesystem

[Karl T. K. <ka...@pr...>]

On Wed, May 16, 2001 at 02:19:18PM -0400, Andrew Molloy wrote:
> I think you meant lin...@li...

Yes of course I did.


> Thanks, I have now semi-successfully gotten the DC to boot.  I used the 
> ip= setting and it mounted the NFS root filesystem.  Unfortunately, it 
> seems to be mounting read-only, so I get a lot of errors during the boot 
> process.  The root filesystem I am using is the Debian-based one from 
> ftp://m17n.org/pub/super-h/debian-unstable/superh/tar+gz/ .
> I examined the files in there, and the permissions seem normal, so I 
> think it's an NFS problem.

Try mounting the NFS share from another machine (or from the NFS server
itself, for that matter) to see if you actually can write to the
directories there (I'd assume you can, but doublecheck nevertheless).

Also, there might be faster, more interactive help on #linuxdc on
irc.openprojects.net

Karl T

[linuxdc-dev] Re: DC NFS root filesystem

[Andrew M. <amo...@st...>]

I think you meant lin...@li...

Thanks, I have now semi-successfully gotten the DC to boot.  I used the 
ip= setting and it mounted the NFS root filesystem.  Unfortunately, it 
seems to be mounting read-only, so I get a lot of errors during the boot 
process.  The root filesystem I am using is the Debian-based one from 
ftp://m17n.org/pub/super-h/debian-unstable/superh/tar+gz/ .
I examined the files in there, and the permissions seem normal, so I 
think it's an NFS problem.  The distribution also seems to be missing a 
few files that the startup scripts are expecting.

"options" :
root=/dev/nfs mem=16M video=pvrdc:640x480-32 
nfsroot=192.168.0.3:/mnt/dcnfs \
ip=192.168.0.4:192.168.0.3:192.168.0.3:255.255.255.0:::

"/etc/exports" :
/mnt/dcnfs 192.168.0.4(rw,no_root_squash)

192.168.0.4 is the DC
192.168.0.3 is the NFS server
Hardware is listed at bottom.

Thanks for the help,
Andrew Molloy


Karl Trygve Kalleberg wrote:

>As I've not had the chance to toy around with booting NFS on the DC
>myself yet (Haven't got the BBA), I'm forwarding this to the list.
>
>However, I wouldn't think it is too different from booting with NFS 
>on an x86, which I've done a few times before, so here's my dollar's worth
>of advice (ymmv, of course):
>
>In /etc/exports, I have:
>/local/karltk/nfsboot pudding.local(rw,insecure,no_root_squash)
>
>In /etc/hosts, I have:
>192.168.1.198   pudding.local   pudding
>
>The kernel parameters I use are (on one line, remove the \):
>nfsroot=192.168.1.199:/local/karltk/nfsboot \
>ip=192.168.1.198:192.168.1.199:192.168.1.199:255.255.255.0:pudding::
>
>I've had a few problems with BOOTP and RARP on 2.4.3 and 2.4.4 (got the
>101 error below), but when I specified all IPs explicitly in the ip=
>parameter sequence, it worked.
>
>192.168.1.199 is the NFS server.
>192.168.1.198 is the NFS client.
>
>
>Hope this helps a bit, at least.
>
>Kind regards,
>
>Karl T
>
>
>--Forwarded message from Andrew Molloy <amolloy1 at stevens dash tech dot edu> --
>
>Hi,
>
>I'm trying to get my Dreamcast to run linux.  I can get it to boot 
>successfully over the broadband adapter via dcload-ip.  I've been unable 
>to mount the root filesystem via NFS though.  This could just be that I 
>can't get the syntax right in my options file, or it might be or 
>portmapper problem, but I think the problem is on the DC side since I 
>can't get it to mount from two different servers.
>
>Thanks for any help,
>Andrew Molloy
>
>
>The error on the Dreamcast (manaully typed in):
>
>Looking up port of RPC 100003/2 on 192.168.0.3
>RPC: sendmsg returned error 101
>portmap: RPC call returned error 101
>Root-NFS: Unable to get nfsd port number from server, using default
>Looking up port of RPC 10005/2 on 192.168.0.3
>RPC: sendmsg returned error 101
>Root-NFS: Unable to get mountd port number from server, using default
>RPC: sendmsg returned error 101
>mount: RPC call returned erorr 101
>Root-NFS: Server returned error -101 while mounting /mnt/dcnfs
>VFS: Unable to mount root fs via NFS, trying floppy.
>VFS: Cannot open root device "nfs" or 02:00
>Please append a correct "root=" boot option
>Kernel panic: VFS: Unable to mount root fs on 02:00
>
>my "options" file:
>root=/dev/nfs mem=16M video=pvr2dc:640x480-32 nfsroot=192.168.0.3:/mnt/dcnfs
>
>relevant parts from my ".config" file:
>CONFIG_PCI=y
>CONFIG_BLK_DEV_LOOP=y
>CONFIG_BLK_DEV_NBD=y
>CONFIG_BLK_DEV_RAM=y
>CONFIG_BLK_DEV_RAM_SIZE=4096
>CONFIG_BLK_DEV_INITRD=y
>CONFIG_PACKET=y
>CONFIG_PACKET_MMAP=y
>CONFIG_NETLINK=y
>CONFIG_UNIX=y
>CONFIG_INET=y
>CONFIG_IP_PNP=y
>CONFIG_NETDEVICES=y
>CONFIG_NET_ETHERNET=y
>CONFIG_NET_PCI=y
>CONFIG_8139TOO=y
>CONFIG_INPUT=y
>CONFIG_INPUT_KEYBDEV=y
>CONFIG_INPUT_MOUSEDEV=y
>CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
>CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
>CONFIG_INPUT_JOYDEV=y
>CONFIG_INPUT_EVDEV=y
>CONFIG_MAPLE_KEYBOARD=y
>CONFIG_MAPLE_MOUSE=y
>#
># Network File Systems
>#
># CONFIG_CODA_FS is not set
>CONFIG_NFS_FS=y
>CONFIG_NFS_V3=y
>CONFIG_ROOT_NFS=y
># CONFIG_NFSD is not set
>CONFIG_SUNRPC=y
>CONFIG_LOCKD=y
>CONFIG_LOCKD_V4=y
># CONFIG_SMB_FS is not set
># CONFIG_NCP_FS is not set
>
>
>my hardware:
>Dreamcast   -  192.168.0.4
>Broadband Adapter
>VGA Adapter
>1 Joystick
>1 Mouse
>1 Keyboard
>1 Mega-Memory Card (4 sets of 200 blocks if I recall correctly)
>
>nfs-server #1   -  192.168.0.3
>Redhat 7.0
>portmap-4.0-29
>/etc/exports = /mnt/dcnfs 192.168.0.4(rw)
>
>nfs-server #2   -  192.168.0.2
>Snap Server  (basically a hard drive on the network, built for NFS 
>sharing, I have successfuly NFS-mounted other shares from this server)
>
>
>----- End forwarded message -----
>

Re: [linuxdc-dev] Debian packages of the sh4 tools ready for testing

[M. R. B. <mr...@li...>]

* Karl Trygve Kalleberg <ka...@pr...> on Wed, May 16, 2001:

> 
> If you're an adventurous soul, with debian on your box, you might want to
> add the line
> 
> deb http://io.prosalg.no/~karltk/linuxdc unstable main
> 
> to your /etc/apt/sources.list
> 
> Then do apt-get install gcc-sh4-linux, and enjoy the cross compiler
> as much as I do ;)
> 

I'm able to install binutils-sh4-linux just fine, but doing an apt-get
install of gcc-sh4-linux results in the following:

Sorry, but the following packages have unmet dependencies:
  gcc-sh4-linux: Depends: libc6 (>= 2.2.2-2) but 2.2.3-1 is to be installed

Also, if binutils-sh4-linux is already installed, and I try to install
gcc-sh4-linux, I get this:

Sorry, but the following packages have unmet dependencies:
  gcc-sh4-linux: Depends: libc6 (>= 2.2.2-2) but 2.2.3-1 is to be installed
                 Depends: binutils-sh4-linux (>= 010515-1) but 010515-1 is to
be installed
E: Sorry, broken packages

I'm running debian unstable.

> Bugs should be reported at:
> http://sourceforge.net/tracker/?atid=114986&group_id=14986&func=browse
> 
> assign them to 'karltk', and I'll get right on them.
> 

Cool!  The bug has been assigned... ;-)

M. R.

[linuxdc-dev] Debian packages of the sh4 tools ready for testing

[Karl T. K. <ka...@pr...>]

It's Wed May 16 05:57:30 CEST 2001, the sun would be getting up if it
wasn't for the clouds, and I've conquered the debian package system, at
least temporarily.

If you're an adventurous soul, with debian on your box, you might want to
add the line

deb http://io.prosalg.no/~karltk/linuxdc unstable main

to your /etc/apt/sources.list

Then do apt-get install gcc-sh4-linux, and enjoy the cross compiler
as much as I do ;)

Bugs should be reported at:
http://sourceforge.net/tracker/?atid=114986&group_id=14986&func=browse

assign them to 'karltk', and I'll get right on them.


Just have to take nap first...


Cheers,

Karl T

Re: [linuxdc-dev] IDE interface

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

Too bad I am an idiot when it comes to electronics, schematics, and
vocabulary. I would love to rig one of these together

----- Original Message -----
From: "Karl Trygve Kalleberg" <ka...@pr...>
To: <lin...@li...>
Sent: Tuesday, May 15, 2001 10:33 AM
Subject: [linuxdc-dev] IDE interface


>
> Anybody want to build one of these for me ? ;p
>
> http://members.nbci.com/_bitmaster_/dc/dc-ide.html
>
>
> Btw, the NetBSD guys also have drivers (we don't, ... yet)
>
> http://www.ma.nma.ne.jp/~ikehara/dc/dcwdc.html
>
>
> Regards,
>
> Karl T
>
> _______________________________________________
> Linuxdc-dev mailing list
> Lin...@li...
> http://lists.sourceforge.net/lists/listinfo/linuxdc-dev


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

[linuxdc-dev] IDE interface

[Karl T. K. <ka...@pr...>]

Anybody want to build one of these for me ? ;p

http://members.nbci.com/_bitmaster_/dc/dc-ide.html


Btw, the NetBSD guys also have drivers (we don't, ... yet)

http://www.ma.nma.ne.jp/~ikehara/dc/dcwdc.html


Regards,

Karl T

Re: [linuxdc-dev] Hi

[Robert <da...@ne...>]

> I wouldn't trust Java any further than I could throw
> it, and believe me, I'd like to throw it, far.. far.. away.
> 
> Regards,
> 
> -- 
> Paul Mundt <pm...@mv...>
> MontaVista Software, Inc.
> 

Hey now, lets play nice and ignore the tendency to fear that
which we do not understand ;-)

Rob.

Re: [linuxdc-dev] Hi

[Paul M. <pm...@mv...>]

On Mon, May 07, 2001 at 09:29:43PM -0400, Tommy Odom wrote:
> cvspserver listens on 2401, atleast on my linux.  I'm not positive that is
> the problem but worth mentioning I suppose.
>=20
Good point. It should also be checked if this problem is persistent even
with a regular CVS connection. This could likely just be a jCVS specific
problem. And in fact, I wouldn't doubt it. My guess is that jCVS runs off
and does its own thing instead of obeying environment variables like the
CVSROOT and the CVS_RSH. I wouldn't trust Java any further than I could thr=
ow
it, and believe me, I'd like to throw it, far.. far.. away.

Regards,

--=20
Paul Mundt <pm...@mv...>
MontaVista Software, Inc.

Re: [linuxdc-dev] Hi

[Tommy O. <tp...@un...>]

Hey i saw you talking to mrbrown on irc about the jCVS problem, one thing
I noticed that might be a problem is the following:
24...@cv...

cvspserver listens on 2401, atleast on my linux.  I'm not positive that is
the problem but worth mentioning I suppose.

Tommy Odom

On Sat, 5 May 2001, Fr=E9d=E9ric BOYER wrote:

> I can't access the source code repository from jCVS.
>=20
> I use the following parameters :=20
> - module : linux
> - CVS server : cvs.linuxdc.sourceforge.net
> - CVS repository : /cvsroot/linuxdc=20
> - CO directory : ...
> - no arguments
>=20
> - login : Anonymous
> - passwd : none
>=20
> What's wrong ?
>=20
> ciao
>=20
> Fr=E9d=E9ric.
>=20

Re: [linuxdc-dev] Swapping over network

[Oliver M . B. <ol...@go...>]

On Mon, May 07, 2001 at 12:59:08AM +0200, Karl Trygve Kalleberg <ka...@pr...> wrote...
> On Sun, May 06, 2001 at 10:04:33AM +0200, Oliver M . Bolzer wrote:
> > Hi!
> 
> Great to see a debianer on the job. Can we arrange to set up some kind of
> public repository with packages, both compiled and in source form, so that
> more people than just you can help out ? 

Actually I'm not the first one. Takeshi YAEGASHI and Mutsumi ISHIKAWA
had been going long before I entered the game.

And except the kernel, there is not much special about the Dreamcast. It
just runs the normal stuff for SH. The only thing might be, that we are
currently compiling for SH3 as SH3 code would run on the SH4 but not
vice versa, until FPU emulation has been implemented.

Currently available package repositories are:

http://hanzubon.org/Linux/Debian/SH/
Current status and packages which need patches to build. This includes
xlibs (which many packages Build-Depends:) and the X-Server is expected
soon. Also a list of packages that are not up-to-date with the official
Debian archive (quinn-diff)

ftp://ftp.m17n.org/pub/super-h/debian-unstable/superh/
starting point for Debian/SH stuff. Basic packages, bast.tgz and 
tarballs for pretty recent GCC CVS snapshots.

http://ftp.<yourcountry>.debian.org/debian/dists/unstable/main/binary-sh/
Don't look in the subdirs (they ought to be removed) but in the Packages
files for packages that can pulled off the official Debian archives. This
includes packages which didn't need to be modifies to compile. This has
stopped somewhat as work is begin done on propper gcc packages, as with
the new shared libgcc, all packages need to depend on libgcc_s.so, which
is not available as a package, yet, and all packages would break horribly.
This place would make more sense once, we get APT working.


There are mostly 3 things that are hindering the porting to go into full
speed:

- No gcc packages. The compiler has to be installed by hand, either
  self-compiled or buinary tar.gz from m17n.org . There are gcc-3.0pre packages
  in Debian but SH needs gcc-3.1 (HEAD) from CVS and there are reservation for
  putting an unstable compiler into the distribution. If we could get a
  arch-specific clean diff against gcc-3.0, could be included ASAP.
  Takeshi YAEGASHI working on it, because we NEED a libgcc.deb to restart
  uploading stuff to the official archives

- X: lots and lots of stuff depends on xlibs. Not only X software but also
     things like TeX and groff Build-Depend on xlibs and even most of the
     basic packages depend on either TeX or groff for documentation.
     First X packages have been created by Mutsumi ISHIKAWA just yesterday.

- APT: what makes Debian so beautiful. Currently work is going on to port
       it to gcc-3.x . SH is not the only architecture needing this, and
       there is already a (not-yet-complete) patch floating around. Once
       apt works, Debian has all the software (quinn-diff, wanna-build
       buildd and sbuild) that can easily be set up for distributed
       auto-building and package reservation for individual porters.

That's about the status I can currently think of. If anybody wants to
help, there is a debian-superh mailing list, which you can join.
See http://lists.debian.org/


# So off I go to burn my self a boot CD with a NBD enabled kernel
-- 
	Oliver M. Bolzer
	ol...@go...

GPG (PGP) Fingerprint = 621B 52F6 2AC1 36DB 8761  018F 8786 87AD EF50 D1FF

Re: [linuxdc-dev] Swapping over network

[Oliver M . B. <ol...@go...>]

On Sun, May 06, 2001 at 03:58:54PM -0700, Paul Mundt <pm...@mv...> wr=
ote...
=20
> I don't recall if the swap over nbd stuff was ever accepted into Linus' t=
ree
> though, so you might want to consult the nbd site before continuing. For =
the
> most part this method works pretty good.

The newest patch I could find was abainst 2.3.99 and I see stuff that looks
 like the same code evelved in the current tree.

http://atrey.karlin.mff.cuni.cz/~pavel/nbd/nbd.swap-patch.23





--=20
	Oliver M. Bolzer
	ol...@go...

GPG (PGP) Fingerprint =3D 621B 52F6 2AC1 36DB 8761  018F 8786 87AD EF50 D1FF

Re: [linuxdc-dev] Swapping over network

[Paul M. <pm...@mv...>]

On Sun, May 06, 2001 at 10:04:33AM +0200, Oliver M . Bolzer wrote:
> What is everybody using for swap over network? I hear there are two
> possibilities :
>=20
> - swap over NFS   ( needs patch, patch isn't very new)

Swapping over NFS really sucks. It's incredibly slow, and highly susceptible
to faults. I've done more reliable swap over IrDA then what NFS has offered.

> - swap over network block device ( patch seems to be included in recent k=
ern.)
>=20
This is the best method I've run into so far. There were some special patch=
es
for doing swap over nbd on the nbd site for awhile that needed to be patched
over top of the existing code in the kernel, and while they were a little b=
it
out of date, it didn't take a whole lot to get them going.

I don't recall if the swap over nbd stuff was ever accepted into Linus' tree
though, so you might want to consult the nbd site before continuing. For the
most part this method works pretty good.

--=20
Paul Mundt <pm...@mv...>
MontaVista Software, Inc.

[linuxdc-dev] Swapping over network

[Oliver M . B. <ol...@de...>]

Hi!

I recently bought myself a full set of japanese Dreamcast, Broadband-Adapter
to aid in the development of Debian/SH. Using BOOTP and NFS-root I'm really
happy and am compiling one Debian package after another but due to the
limited memory on the system and no swap, the system starts really choking
on large native compiles (mostly C++).

What is everybody using for swap over network? I hear there are two
possibilities :

- swap over NFS   ( needs patch, patch isn't very new)
- swap over network block device ( patch seems to be included in recent kern.)

Can anybody share some expirence with these ?

Thanks!


-- 
	Oliver M. Bolzer
	ol...@de...

GPG (PGP) Fingerprint = 621B 52F6 2AC1 36DB 8761  018F 8786 87AD EF50 D1FF

Re: [linuxdc-dev] Hi

[Paul M. <pm...@mv...>]

On Sat, May 05, 2001 at 12:52:35AM +0200, Fr=E9d=E9ric BOYER wrote:
> I can't access the source code repository from jCVS.
>=20
> I use the following parameters :=20
> - login : Anonymous
> - passwd : none
>=20
> What's wrong ?
>=20
CVS is case sensitive, thus "Anonymous" !=3D "anonymous". Also.. anonymous
has to be accessed via pserver as opposed to the rsh/ssh methods. Thus
your root should look something like:

:pserver:ano...@cv...:/cvsroot/linuxdc

Other then that everything looks okay. Do you have some sort of error log
that weilds any kind of useful information? and can you add a -t to the
CVS command for more verbose messages?

Regards,

--=20
Paul Mundt <pm...@mv...>
MontaVista Software, Inc.

Re: [linuxdc-dev] Hi

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

* Fr?d?ric BOYER <bo...@wa...> on Sat, May 05, 2001:

> 
>    I can't access the source code repository from jCVS.
>    

Hmm, is this a Windows program? - never heard of it.  If so, you may want to
try WinCVS, although the link http://www.wincvs.org/ seems to be down
currently.  Vanilla cvs (the command-line version) works fine if you're
using a *nix platform.

M. R.

[linuxdc-dev] Hi

[<bo...@wa...>]

I can't access the source code repository from jCVS.

I use the following parameters :=20
- module : linux
- CVS server : cvs.linuxdc.sourceforge.net
- CVS repository : /cvsroot/linuxdc=20
- CO directory : ...
- no arguments

- login : Anonymous
- passwd : none

What's wrong ?

ciao

Fr=E9d=E9ric.

[linuxdc-dev] [linuxdc-cvs] Missing files at Kernel HOWTO and Tools HOWTO pages

[dong-in <dk...@ea...>]

 Hello,

 I'm trying to build and load linux on Dreamcast.
However, those files such as patches, and configuration files are not
available from the web page.
It simply says "the page cannot be found".
Can somebody help me?

 Thanks,

 Dong-In Kang


_______________________________________________
linuxdc-cvs mailing list
lin...@li...
http://lists.sourceforge.net/lists/listinfo/linuxdc-cvs