linuxdc-dev

[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

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.

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

[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 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