Re: [linuxdc-dev] Newbie questions

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

On Thu, Sep 27, 2001 at 04:08:06PM +0200, edd...@wa... wrote:
> 1) GD-Rom support: I found at some point on the web the information that 
> support was available now, and in the 2.4.10-pre6 kernel you've got some 
> kind of option for GD-Rom support. What is it status? I'd love to get rid 
> of the initrd, actually... :)
> 
There's an ugly hack of a GD-ROM driver in the LinuxSH tree (linuxsh.sf.net)
which is based off an ugly NetBSD driver. It works for the most part, but will
definately be replaced by a cleaner one as time allows. It might be feasible
to use for booting, but I've not tried it, so I can't confirm one way or the
other.

> 2) I'm working with the files used in BG's article, but where can I find 
> new diffs? I guess things move fairly often, do I need to CVS or is there 
> some kind of regular diffs release somewhere?
> 
The way we're doing it now is doing all experimental and new development in
the LinuxDC CVS, then after it's tested and ready to move on, it gets pushed
into the LinuxSH CVS. As far as what's in the LinuxDC CVS, everything is being
done as a drop-in tree, so you need to link it into a stock checkout of the
LinuxSH tree if you really want it. Though new users shouldn't ever be
touching the experimental tree for any reason at all, and we have no intention
of supporting the experimental tree incase a new user has problems with it.

> 3) Do you maintain your own tree for the basic tools 
> (binutils/gcc/libc/kernel) and release from time to time diffs, or are your 
> bug corrections merged inside the main CVS trees?
> 
See above. The only thing that's being maintained is the kernel. The rest of
the stuff just requires occasional patching which generally applies to SH4 in
general, and is better handled through the LinuxSH project.

> 4) A few problems when buiding gcc, for example whent omitting the 
> --with-newlib flag. Hints? BTW, never managed to compile correctly 
> newlib-1.9. Again, hints?
> 
How about posting an error log? What you're implying is -ESOMETHINGWENTWRONG,
which isn't all that useful.

Regards,

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