linuxdc-dev — Developer discussion list

[linuxdc-dev] [PATCH] pvr2dcfb cleanups

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

Hello,

After having read over the pvr2dcfb driver I noticed a few relatively
unimportant issues with it. Namely, it was missing MTRR support, it
was using the old module interface, and debugging wasn't a config
option.

This is a quick simple patch that addresses these issues. It is untested
as it was just written in a few minutes .. a few minutes ago. So you
might just want to run as fast as you can in the opposite direction of
it, but feel free to try it anyways.

Regards,

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

[linuxdc-dev] Kernel Patch for MAPLE BUS, keyboard and mouse support available

[Jeff T. <jw...@me...>]

I have made a preliminary source code patch available on my web site for
the CVS LinuxDC kernel.  Once it's been tested and people are happy with
it, it will hopefully get put into the CVS tree.

You can obtain the patch from http://www.cupug.org/ in the Dreamcast
section.

This patch adds:

1) MAPLE bus device driver.
   Scans bus for devices.
   Allows device drivers for the bus to register with it
   Notifies device drivers when they need to manage a device
   Supports hot swapping
   Uses polling method for checking the bus for data
2) MAPLE Keyboard support
3) MAPLE Mouse support

Things to do: :)
1) Test
2) Switch from polling to interrupt based system
3) Have all maple devices send their messages through the maple bus driver
rather than directly to the bus.  This will allow the bus driver to blast
them all out in one dma trasnfer.  The bus driver will also notify devices
when information is available for them.
4) Write controller and other device drivers
5) More commenting
6) Performance review of the code

Enjoy!

Jeff Thompson

Re: [linuxdc-dev] New member

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

* messiah <me...@op...> on Mon, Mar 26, 2001:

> I have recently joined as a member on www.linuxdc.org and was wondering what
> projects still need to be done?
> 
> I am new to the Dreamcast world, but I have developed for Debian and would
> love to experiment with Dreamcast Linux development.
> 

Wow, I've always wanted to tread the distro waters, even thought of rolling
my own once :).

Anyways, as far as the LinuxDC kernel, AFAIK Maple Bus support (input for
the keyboards, joysticks, mouse, and other connectable peripherals) is
currently being worked on, and I'm about to work on a GD-ROM driver and an
accelerated frame buffer.  The only thing that no one has volunteered for
kernel-wise would be the sound subsystem.

The other major LinuxDC project would be porting apps to the SH4.  There's
actually a developer porting Debian to the SuperH (ftp.m17n.org).  I'd also
like to see an effort started where people would submit patches/tarballs of
libraries and apps that they've been able to sucessfully cross-compile to
LinuxDC.

M. R.

[linuxdc-dev] New member

[messiah <me...@op...>]

I have recently joined as a member on www.linuxdc.org and was wondering what
projects still need to be done?

I am new to the Dreamcast world, but I have developed for Debian and would
love to experiment with Dreamcast Linux development.

-Danny Rodriguez

[linuxdc-dev] Bootable kernel CD image?

[<bg...@op...>]

Any ideas on how to make a bootable linuxdc CD?

b.g.
-- 
Bill Gatliff
bg...@op...

[linuxdc-dev] Updates to the website

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

Hi all.

I've done a few updates to the web site:

) Kernel HOWTO, TODO list and Tools HOWTO are now 'integrated' into the
  PHP Nuke system.
) a buildsite.sh shell script in /home/groups/linuxdc takes care of
  updating all the necessary stuff from CVS, copying some files from the
  docs module (HOWTOs and TODO-list) over into the site and using
  the correct config.php
) The TODO list is now recent.
) The IRC logs are HTMLized every 30 minutes and are linked from our
  website.

I'll spend time installing and testing our code now, and updating the
tools and installation HOWTOs to reflect the latest stuff done by Marcus.



Regards,

Karl T

[linuxdc-dev] another add on device for DC?

[gee308 <ge...@me...>]

DC of Japan has released a karaoke add on.  Anyone have more info about the
device's hardware specs?
Jason
http://dreamcast.ign.com/news/32384.html

Re: [linuxdc-dev] BBA support finished

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

* M. R. Brown <mr...@li...> on Tue, Mar 13, 2001:

> I've completed Broadband Adapter support and it's now in the latest CVS
> snapshot.  I'm currently working on docs that detail booting this kernel
> with BusyBox and so on.
> 

A small bug has been fixed that caused rx errors (highly visible when using
NFS) within the ethernet driver.  I suggest anyone who had updated before
today update again :).

There is a current bug that I'm trying to track down that prevents ethernet
from working when booting from CD or uploading using a serial cable.  I'll
post to the list as soon as this corrected.

M. R.

[linuxdc-dev] BBA support finished

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

I've completed Broadband Adapter support and it's now in the latest CVS
snapshot.  I'm currently working on docs that detail booting this kernel
with BusyBox and so on.

Also the FAQ for LinuxDC has been updated - please let Karl or myself know
of any additions you would like to see.  The same goes for documentation.

M. R.

[linuxdc-dev] Serial cable

[John W. <lin...@ho...>]

Due to overburdening work, I am not able to spend as much time as I had 
hoped for on this project.  I got all the components to create a serial 
cable for it and will be more than happy to send them (it isn't made, just 
have raw materials) to someone for the price I paid for them.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

[linuxdc-dev] Prelim. PCI/Broadband support

[<mrb...@0x...>]

There is now *preliminary* Sega Broadband Adapter support in the latest CVS
update.  Initialization of PCI and the ethernet chip seems to work, however
I'm having problems with interrupts so the device is currently
non-functional :(.

If someone gets a chance to look at/test the code please do.  Also, if you
can pinpoint where my interrupt-handling, etc (arch/sh/kernel/pci_gaps.c)
has gone awry, please let me know.  The driver broke for me when kernel IP
auto-configuration tried to send a BOOTP request to the network.  The
RTL8139 driver is then flooded with pci bus errors (2210), so I'm probably
not acknowledging something somewhere.  I'll be looking into fixing this later
on this evening.

M. R.

Re: [linuxdc-dev] CD burning problems (bad drive?)

[John W. <lin...@ho...>]

I have had success in burning this, but I used the script from the README on 
marcus' site.  That script was much smaller; two lines, than what you have 
here.


>From: ac...@ac... (Andrew Church)
>To: lin...@li...
>Subject: [linuxdc-dev] CD burning problems (bad drive?)
>Date: Thu, 08 Mar 2001 15:35:37 JST
>
>      I've been trying to burn the serialslave (from Marcus' site) onto
>CD, but my Dreamcast is refusing to boot it.  The script I'm using is
>below; is there anything wrong with it or do I need to look for a
>different CD writer?  Incidentally, I've tried specifying padsize=0 or
>not for cdrecord, specifying -C or not for mkisofs, running "cdrecord
>-msinfo" or giving the value (known from previous writes) directly,
>and taking the disc out or not between writes, but nothing seems to
>work; the Dreamcast goes to the audio CD screen (2 tracks, 2:42) if I
>boot with the cover closed, and if I try "play" from the menu it just
>resets.
>
>      System info:
>	- OS: Linux (2.2.16)
>	- CD writer: Smart and Friendly CD-R4012 (SCSI drive; the
>	             cdrecord README says it's supported, and it works
>	             fine for ordinary audio/data writing)
>	- cdrecord: version 1.9
>
>Script:
>-------------------------------------
>#!/bin/sh
>
>tmpdir=/tmp/makedisc
>dir=`echo "$1" | sed 's/\/$//'`
>if [ "$2" ] ; then
>	ipbin="$2"
>	exclude=""
>else
>	ipbin="$dir/IP.BIN"
>	exclude="-x $ipbin"
>fi
>
>if [ $# -lt 1 -o ! -f "$ipbin" ] ; then
>	echo >&2 "Usage: $0 <fs-dir> [IP.BIN-path]"
>	echo >&2 "If IP.BIN-path is not specified, it must be in <fs-dir>."
>	exit 1
>fi
>
>rm -rf $tmpdir
>mkdir $tmpdir || exit 1
>dd </dev/zero bs=2352 count=300 >$tmpdir/audio.raw
>cdrecord -multi -audio $tmpdir/audio.raw
>rm -f $tmpdir/audio.raw
>
>msinfo=`cdrecord -msinfo`
>if [ ! "$msinfo" ] ; then
>	echo >&2 'cdrecord -msinfo failed!  Aborting.'
>	exit 1
>fi
>mkisofs -l -C $msinfo -o $tmpdir/disc.iso $exclude $1
>dd if="$ipbin" bs=2048 count=16 of=$tmpdir/disc.iso conv=notrunc
>cdrecord -multi -xa1 $tmpdir/disc.iso
>
>rm -rf $tmpdir
>-------------------------------------
>
>   --Andrew Church
>     ac...@ac... | New address - please note.
>     http://achurch.org/ | ƒ[ƒ‹ƒAƒhƒŒƒX‚ª•Ï‚í‚è‚Ü‚µ‚½B
>
>_______________________________________________
>Linuxdc-dev mailing list
>Lin...@li...
>http://lists.sourceforge.net/lists/listinfo/linuxdc-dev

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com

[linuxdc-dev] New site alias, new poll

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

Hi all.

Marcus R. Brown has secured us the linuxdc.org domain. Our web address is now 
www.linuxdc.org in addition to what we already have.

The new poll that has been put up shows clearly that people want 

1) Broadband adapter support
2) Keyboard support


And strangely enough that's what we're working on ;)

If anybody could checkout the docs module from CVS and give us feedback, that'd 
be just great, since the installation process is a bit difficult right now, and we'd
like to document it as lucidly as possible.

Regards,

Karl T

Re: [linuxdc-dev] CD burning problems (bad drive?)

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

On Thu, Mar 08, 2001 at 03:35:37PM +0900, Andrew Church wrote:

> rm -rf $tmpdir
> mkdir $tmpdir || exit 1
> dd </dev/zero bs=2352 count=300 >$tmpdir/audio.raw
> cdrecord -multi -audio $tmpdir/audio.raw
> rm -f $tmpdir/audio.raw
> 
> msinfo=`cdrecord -msinfo`
> if [ ! "$msinfo" ] ; then
> 	echo >&2 'cdrecord -msinfo failed!  Aborting.'
> 	exit 1
> fi
> mkisofs -l -C $msinfo -o $tmpdir/disc.iso $exclude $1

I see you specify -l, which I don't. It should not have any influence, but 
I'd advise you to try without it (and keep your files within 8.3 DOS naming
conventions).

> dd if="$ipbin" bs=2048 count=16 of=$tmpdir/disc.iso conv=notrunc
> cdrecord -multi -xa1 $tmpdir/disc.iso

I don't specify -multi here.


Those are the only two differences I could find between your script and the
scripts/Makefiles I've been using.


But, if you're going to toy around with linuxdc, we recommend you get and
use dcload, available from http://www.cerc.utexas.edu/~andrewk/dc/

In the make-dc dir is a Makefile that burns the CD.

Regards, 
Karl T

[linuxdc-dev] CD burning problems (bad drive?)

[<ac...@ac...>]

     I've been trying to burn the serialslave (from Marcus' site) onto
CD, but my Dreamcast is refusing to boot it.  The script I'm using is
below; is there anything wrong with it or do I need to look for a
different CD writer?  Incidentally, I've tried specifying padsize=0 or
not for cdrecord, specifying -C or not for mkisofs, running "cdrecord
-msinfo" or giving the value (known from previous writes) directly,
and taking the disc out or not between writes, but nothing seems to
work; the Dreamcast goes to the audio CD screen (2 tracks, 2:42) if I
boot with the cover closed, and if I try "play" from the menu it just
resets.

     System info:
	- OS: Linux (2.2.16)
	- CD writer: Smart and Friendly CD-R4012 (SCSI drive; the
	             cdrecord README says it's supported, and it works
	             fine for ordinary audio/data writing)
	- cdrecord: version 1.9

Script:
-------------------------------------
#!/bin/sh

tmpdir=/tmp/makedisc
dir=`echo "$1" | sed 's/\/$//'`
if [ "$2" ] ; then
	ipbin="$2"
	exclude=""
else
	ipbin="$dir/IP.BIN"
	exclude="-x $ipbin"
fi

if [ $# -lt 1 -o ! -f "$ipbin" ] ; then
	echo >&2 "Usage: $0 <fs-dir> [IP.BIN-path]"
	echo >&2 "If IP.BIN-path is not specified, it must be in <fs-dir>."
	exit 1
fi

rm -rf $tmpdir
mkdir $tmpdir || exit 1
dd </dev/zero bs=2352 count=300 >$tmpdir/audio.raw
cdrecord -multi -audio $tmpdir/audio.raw
rm -f $tmpdir/audio.raw

msinfo=`cdrecord -msinfo`
if [ ! "$msinfo" ] ; then
	echo >&2 'cdrecord -msinfo failed!  Aborting.'
	exit 1
fi
mkisofs -l -C $msinfo -o $tmpdir/disc.iso $exclude $1
dd if="$ipbin" bs=2048 count=16 of=$tmpdir/disc.iso conv=notrunc
cdrecord -multi -xa1 $tmpdir/disc.iso

rm -rf $tmpdir
-------------------------------------

  --Andrew Church
    ac...@ac... | New address - please note.
    http://achurch.org/ | メールアドレスが変わりました。

[linuxdc-dev] CVS Update - Framebuffer support

[M. R. B. <ma...@uw...>]

I've added Dreamcast framebuffer support to CVS.  Currently it only
supports 640x480 @ 16, 24, and 32bpp, but that's only becasue I haven't
sat down and calculated each particular mode yet.

The long-neglected HOWTOs for tool building/uploading, etc. are next on my
list, before I work on any more drivers :).  If anybody is successful with
the current snapshot (it should build fine, just follow the instructions
in my previous post), please send me an e-mail and let me know what
does/doesn't work.  Thanks.

M. R.

[linuxdc-dev] Kernel update 2001-02-21 (fwd)

[M. R. B. <ma...@uw...>]

I guess I was up a little to late, I left off the 's', and it bounced,
sorry to keep y'all waiting :).

M. R.



---------- Forwarded message ----------
Date: Wed, 21 Feb 2001 10:12:13 -0600 (CST)
From: "M. R. Brown" <ma...@uw...>
To: lin...@li...
Subject: Kernel update 2001-02-21

Hey all,

I've submitted a batch of updates to CVS; now the kernel isn't broken by
default :).  All that's there right now is the necessary RTC stuff to keep
the kernel from hanging, and low-level interrupt routines for the
PowerVR2DC chip (or G2 bus or whatever).  Anyway, I've tested it via
serial, and ethernet+serial.  Here's a brief synopsis:

- I compiled my tree using a fairly recent snapshot of gcc.  My version of
  binutils is 2.10.1.  HOWTOs for tool-building are in the works, I'd
  figure the code would look better first :)

- gcc has a "bug" with the flag -m4-nofpu that's specified in
  arch/sh/Makefile.  Either apply my attached patch, or change the lines
  that read -m4-nofpu to -m4.

- I've also attached a .config file that you can use, it has everything
  completely stripped out.

- If you're ready to build, do a:
  $ make ARCH=sh dep
  $ make -j3 ARCH=sh zImage

- When using a compressed kernel image, a real bootloader places ramdisk
  and other kernel parameters as predesignated locations in RAM.  Well, we
  don't have one of those yet :).  So instead, I've attached a file called
  page0.  It's purpose is to provide default parameters to start a serial
  console, and specify the system RAM size (approx. 16M).

- Whether you have ethernet (BBA) or serial cable, the best tool for
  uploading is Andrew K.'s dcload.  Because both versions have the same
  name and take the same arguments, the following commands apply to both
  sets of tools:

  $ dc-tool -a 0x8c011000 -u page0
  # This loads the kernel parameters
  $ dc-tool -n -a 0x8c220000 -x arch/sh/boot/zImage
  # And this loads the compressed kernel image and executes it.

  Note: if you use the serial version of dcload then specify the -p option
  to see the kernel boot messages.  If you have a combination of
  ethernet+serial, specify the -n option to dcload while your terminal is
  listening on your COM port.  And if you only have ethernet, well, you
  won't get anything :)

  For those who don't have either, here's the dmesg output:

Linux version 2.4.0 (mrbrown@alphaflight) (gcc version 3.1 20010220 (experimental)) #1 Wed Feb 21 09:31:05 CST 2001
On node 0 totalpages: 4080
zone(0): 4080 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/ram mem=16320k console=ttySC1,57600
CPU clock: 199.50MHz
Bus clock: 99.75MHz
Module clock: 49.87MHz
Interval = 124692
Calibrating delay loop... 199.06 BogoMIPS
Memory: 15404k/16320k available (463k kernel code, 916k reserved, 17k data, 24k init)
Dentry-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 1024 (order: 1, 8192 bytes)
CPU: SH7750
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing PowerVR2DC v1.1 at 0xa05f0000 (interrupts on IRQ 9, 96 total)
Starting kswapd v1.8
block: queued sectors max/low 10176kB/3392kB, 64 slots per queue
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
SuperH SCI(F) driver initialized
ttySC0 at 0xffe00000 is a SCI
ttySC1 at 0xffe80000 is a SCIF
VFS: Cannot open root device "ram" or 01:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 01:00


Good night! :)

M. R.

Re: [linuxdc-dev] Updates to UDCTM and the TODO list

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

On Mon, Feb 19, 2001 at 08:27:16AM -0800, Neil Bliss wrote:
> Once upon a time, karltk said...
> > If anybody has either a guideline for compiling the build tools and/or a
> > pre-built build toolchain, mail me, and I'll put it up. It would be preferrable
> > to have both of these for the people who don't run x86 hardware.
> 
> This is where I've been blocked.  All my way bitchin hardware (at work) is all
> sparc/solaris, and I can't seem to get the sh4 gcc stuff to build at all under
> solaris.  Any pointers or tips would be greatly appreciated.

Can't give you any pointers just now, but I'll try to build the toolchain
on Solaris/Sparc tomorrow and tell you how it went. I don't really know if
it's all supposed to compile properly on sparc just now. Do you use gcc or
SparcWorks CC ? (I'll test both).


Regards,

Karl T

Re: [linuxdc-dev] Updates to UDCTM and the TODO list

[Neil B. <yo...@in...>]

Once upon a time, karltk said...
> If anybody has either a guideline for compiling the build tools and/or a
> pre-built build toolchain, mail me, and I'll put it up. It would be preferrable
> to have both of these for the people who don't run x86 hardware.

This is where I've been blocked.  All my way bitchin hardware (at work) is all
sparc/solaris, and I can't seem to get the sh4 gcc stuff to build at all under
solaris.  Any pointers or tips would be greatly appreciated.

-- 
Neil Bliss - Integratus Customer Support
toy.rusher.com/yoda -- Yow!  I am having fun!!

Re: [linuxdc-dev] Updates to UDCTM and the TODO list

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

On Sun, Feb 18, 2001 at 10:19:31PM -0600, M. R. Brown wrote:

> I had a "roadmap" going, but like mostly everything else so far, time has
> stolen that one :).  I have some ideas as well as areas that need to be
> worked on, some things include building tools, and creating RAMDISK
> images, etc.

We should put up our toolchain, scripts, pre-built ramdisks and images on the
SF ftp/http as they become available.

If anybody has either a guideline for compiling the build tools and/or a
pre-built build toolchain, mail me, and I'll put it up. It would be preferrable
to have both of these for the people who don't run x86 hardware.


Regards,

Karl T

Re: [linuxdc-dev] Updates to UDCTM and the TODO list

[M. R. B. <ma...@uw...>]

On Sun, 18 Feb 2001, Karl Trygve Kalleberg wrote:

[...]
> 
> It doesn't look sexy. Sorry about that.
> 
> Its purpose is to be able to point to it and say 'Foo is responsible for that part, go talk to him about
> that'. The basis for the list is what you guys have told me before. Both Rene and Marcus Brown seem to be
> a bit busy as of late, so they might be willing to let other people take over their claimed areas.
> 

Heh, not busy any longer, promise :).

> I hereby proclaim myself the CVS and TODO-list guy until anybody fiercely objects. That means that you if
> you want to do anything not mentioned on the TODO-list and you're uncertain anybody else is working on it,
> talk to me. 
> 

I had a "roadmap" going, but like mostly everything else so far, time has
stolen that one :).  I have some ideas as well as areas that need to be
worked on, some things include building tools, and creating RAMDISK
images, etc.

> Also, send any and patches and requests for syncing the CVS with whatever to me. It seems that every developer
> for some reason maintains his own tree completely separately from our own CVS. 
>

Yeah, we need guidelines on submission, this is a great start.  I'm
working on a script to merge the current kernel (reflected in LinuxSH's
tree) with ours, hopefully to be setup on a daily basis.  The thing with
that is to make sure we don't step on LinuxSH's code (mostly everything in
the arch/sh tree, with a few misc. drivers).

Anyone who is on this list is welcome to submit any ideas, code, rants, to
the list as we try to get the ball rolling.  In particular any thoughts on
how to implement specifc subsystem drivers, e.g. GD-ROM, FB, AICA audio,
input, ethernet - whatever, please post for further discussion.  Hopefully
everyone didn't die off in the two months we (part. I) was in a coma :P.

M. R.

[linuxdc-dev] Updates to UDCTM and the TODO list

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

Hi gang.

Sorry for being so quiet as of late. I've been abroad and I'm also changing jobs so things 
are a bit turbulent.

I managed to steal a few hours, though, and I have update the Unofficial Dreamcast Technical Manual
(UDCTM). It now has a section on the Maple bus and a section the GD-ROM. There isn't much meat in either
section. All I could find was the stuff by Marcus Comstedt and Dan Potter (which is pretty much the same).

If anybody have any more info on these (or other DC-related) topics, don't hesitate to tell me.


About the TODO-list.

It doesn't look sexy. Sorry about that.

Its purpose is to be able to point to it and say 'Foo is responsible for that part, go talk to him about
that'. The basis for the list is what you guys have told me before. Both Rene and Marcus Brown seem to be
a bit busy as of late, so they might be willing to let other people take over their claimed areas.

I hereby proclaim myself the CVS and TODO-list guy until anybody fiercely objects. That means that you if
you want to do anything not mentioned on the TODO-list and you're uncertain anybody else is working on it,
talk to me. 

Also, send any and patches and requests for syncing the CVS with whatever to me. It seems that every developer
for some reason maintains his own tree completely separately from our own CVS. 



Dictatory regards,

Karl T

[linuxdc-dev] [linuxdc-dev]: Net boot linux kernel

[Jeff T. <jw...@me...>]

I have managed to get the CVS kernel booting (by editing some things,
figuring out what the config options should be via make menu config, and
by copying over some files from the firstkernel tar ball). I don't have a
serial cable, but do have the ethernet adapter.  I have obtained and
burned the IP-slave program as well as another network bootloader a friend
of mine wrote (www.openblt.org/dcdev/) and would like to test my builds.
However, I am having very little luck.  Basically things are haning after
the code is loaded.  This could clearly be a badly built kernel, or
possibly something else, so I was wondering if anyone else had done a net
boot and if anyone had a working vmlinux that I could use to test with in
order to get my net setup working and verified first.

I also used the .config from first kernel as a basis for my configuration
(if that is of any help to anyone :) ).

Once I get all of this working, I'd be happy to write up a mini-faq in
order to help anyone else who is trying to work with the CVS tree and
broadband adapters.

Thank you for any help,

Jeff

Jeff Thompson
Software Evangelist and Visionary
Senior Security Analyst
Argus Systems Group, Inc.

Re: [linuxdc-dev] CD booting

[Rene M. <re...@dr...>]

Frapazoid wrote:
> 
> Rene Malmgren wrote:
> 
>
> > Yes, its on the TO-DO list. But right now the PCI birge is on top
> > priotety, the DCROM is next.
> >
> 
> Where can I find the TO-DO list? The TODO file in the kernel source code
> package just
> has a list of error codes... Ones that I can't read. (I'm not a kernel
> programmer...):

Whell it has sort of been discussed on the irc chanel. And in other
varios forums.

But for short it now consists of

1. Getting the permisson to release the FB + KBD support. (I have the
working code but not permission to release yet)
2. Implementing PCI support (witch will give us ethernet)
3. Fixing better docs.
4. Implementing GDROM support
5. Enhansing KBD and FB support.
6. creating sound support.

Right now 1 & 2 are high priorety. 3&4 will come later, and 5 & 6 well
thats the far distent future.

Unfortunately I have been busy at work so my part has been on ice for
now. But that should chage soon.


> 
> >
> > >
> > > Is it possible to run the kernel, the filesystem and all the other
> > > software directly
> > > off the cdr without any serial transfers? Is there a DC linux bootloader
> > > yet?
> >
> > Yes, Yes. But right now the offical kernel only runs on serial console,
> > so there isnt mych point in doing that.
> >
> 
> Is this problem anywhere on the todo list?

Problem?

> 
> > > _______________________________________________
> > > Linuxdc-dev mailing list
> > > Lin...@li...
> > > http://lists.sourceforge.net/lists/listinfo/linuxdc-dev

Re: [linuxdc-dev] cvs and kernel building

[M. R. B. <ma...@uw...>]

On Thu, 8 Feb 2001, Jeff Thompson wrote:

> I recently placed this as a comment to the cvs source being available on
> sourceforge but figured this would be a more appropriate place to put my
> questions.
> 
>  First a note about my setup
> 
> RedHat 6.2
> binutils-sh4-linux-010127-2.i386.rpm
> gcc-sh4-linux-2.97.001120-3.i386.rpm
> gdb-sh-linux-5.0.001127-2.i386.rpm
> 
> Please note that the gcc is actually -2.deb version, but alien increased
> the number
> when I converted it. I was unable to find the -1 version as listed in the
> HOWTO
> document.
>

First off, you will want to change the CFLAGS in arch/sh/Makefile that
specify -m4-nofpu to -m4.  The -m4-nofpu option actually targets the SH3
series (overriding target selection from `make config').  I've addressed
this to the LinuxSH-dev list.  Without this option set to -m4, many, many
things will break.
 
> 
> When I compile the firstkernel tarball's source I get the following error:
> 
> make[1]: Entering directory `/root/box/kernel/arch/sh/kernel'
> sh4-linux-gcc -D__ASSEMBLY__ -D__KERNEL__ -I/root/box/kernel/include -ml
> -m4-nofpu -c -o entry.o entry.S
> entry.S: Assembler messages:
> entry.S:375: Error: must be @(r0,...)
> entry.S:376: Error: must be @(r0,...)
> entry.S:377: Error: must be @(r0,...)
> entry.S:378: Error: must be @(r0,...)
> entry.S:379: Error: must be @(r0,...)
> entry.S:433: Error: must be @(r0,...)
> make[1]: *** [entry.o] Error 1
> make[1]: Leaving directory `/root/box/kernel/arch/sh/kernel'
> make: *** [_dir_arch/sh/kernel] Error 2
> 
> I assume that this is caused by the problems with different gcc versions
> as
> mentioned in the HOWTO document. Has anyone else got this going with this
> version of gcc from m17n.com?
>

This first error is due to the fact that the newer binutils (the ones
you're currently using) are case-insensitive when it comes to register
names.  arch/sh/kernel/entry.S uses macros (R0, SR) which violate this.
There is a fix in the latest LinuxSH kernel, as I write this I'm preparing
to merge changes from LinuxSH's kernel (2.4.1-final) into our slightly
dated LinuxDC kernel.
 
> I also retrieved the cvs source and attempted to compile. In this case I
> get a failure
> in the make dep:
> 
> make[4]: Leaving directory `/root/box/linux/net/bridge'
> make -C core fastdep
> make: Entering an unknown directory
> make: *** core: No such file or directory. Stop.
> make: Leaving an unknown directory
> make[3]: *** [_sfdep_core] Error 2
> make[3]: Leaving directory `/root/box/linux/net'
> make[2]: *** [fastdep] Error 2
> make[2]: Leaving directory `/root/box/linux/net'
> make[1]: *** [_sfdep_net] Error 2
> make[1]: Leaving directory `/root/box/linux'
> make: *** [dep-files] Error 2
> 

Did you remember to do `make ARCH=sh dep' instead of just `make dep'?
When cross-compiling, all make parameters must include ARCH=sh to build
correctly.

[...]
> So, the next question is, has anyone had any luck in building these
> sources? Any
> tips or thoughts are welcome!
> 

The current LinuxDC kernel cannot be built easily (unfortunately).

I haven't gotten around to finishing my own versions of Installation and
Tools HOWTOs, right now it's pretty much "glean from LinuxSH, adapt to
LinuxDC".  I have more time now to start streamlining the process.

> I'll be spending some time this weekend working on these problems and
> trying to get
> things going. I work for a OS level computer security company and have two
> other
> kernel developers who are going to be getting linux going on their systems
> (we want
> to get our security extensions on the dreamcast just for fun!), so
> hopefully we'll be
> able to make a few substantial contributions to the effort.
> 

That's sounds pretty cool.  What kind of security patches do you have?
I'm still debating adding LIDS into my LRP router...

I hope to have gdrom, PCI, maple input, and framebuffer up and running by
next week.  No, I'm not just leeching off of Marcus Comstedt's NetBSD
sources (well, maybe for GD-ROM and PCI ;), but I've been working on FB
and maple input (that conforms to Linux 2.4's Input Core) off and on. 
With Maple input, you'll be able to "hotplug" maple devices, and let the
proper handler (input core or generic maple) take over based on the
device.  More on this later. 

> Thanks for any help!
> 

Heh.  Tell all your kernel hacker friends about us :)

> Jeff
> 
> Jeff Thompson
> Software Evangelist and Visionary
> Senior Security Analyst
> Argus Systems Group, Inc.
> 

M. R.

P.S. BTW, it doesn't look like Rene's DC RTC patches ever made it into the
CVS (?).  I have my own patches, which I'm going to update soon, that has
DC RTC and some low-level PowerVR2DC interrupt handling.