From: Rene M. <re...@li...> - 2000-10-25 13:34:42
|
Thank you very mych for all the help. YAEGASHI Takeshi wrote: > > Currently it can run only on the restricted environment with > initrd. It can handle none of GD-ROM, Audio or Ethernet yet > from lack of sepcs... Yes, all the information I could get was > from Marcus Comstedt's DC site. Ok is information on these chips interesting to the development team? > > > I'm sorry but I cannot release my port publicly, because I'm > working for NAMCO, which has an NDA on Dreamcast with SEGA > (actually I've not learned anything from SEGA under this NDA, > but do they admit this fact?). So I think I need SEGA's > permission to release the port. I see you got the same kind of support over there as we do in Europe ;-). But seriosly, usualy NDAs only cover the things that they hand over to you, and since they havn't... But yours could be different, I only know how its done over here. But i don't want to get you in troubel with your boss. > > >> Q2: Is there an FB device that works with the PowerVR2 GFX. (As I >> understand It the answer i NO) > > > Yes there is. Framebuffer console is now working fine with > SuperH Tux(many thanks to Greg:->). We can login Dreamcast with > keyboard or via serial port. Ok so there is an FB for the DC. In what kernel and where do I find it. (Is it publicly availible?) I tried the 2.4.0-test9 and the CVS kernel from linux-sh but couldnt find FB support. > > > >> Q3: I have heard and seen an someone with an NIC (Network Interface >> Card) but so far haven't had any luck in getting hold of one. Are they >> available in Japan or US? > > > I have one. It can be ordered from SEGA's site(but in Japanese). > > http://www3.csi-msp.com/dcweb/ Ok thet explains it. How do you get one to Europe? My Japanese is about as good as your Swedish ;-). Colud you buy me one (ill wiretransfer you the money in advance and you could send it to me via TNT or something like that.) > > > >> Q4: I managed to download the x86 cross compile tools from >> >> ftp://ftp.m17n.org/pub/linux-sh/debian/packages-i386/ >> >> but for some reason the tools are installed as sh-linux-gcc and not >> sh-linux-gnu-gcc as the kernel expects, why? > > > Because Debian policy expects to be sh-linux-gcc(I heard gnu is > reserved for Debian GNU/Hurd). You can feel free to change the > kernel's Makefile. Ok... Right now I took the easy way out (symlinks) > > > >> Q5: I have downloaded the kernel source from the CVS directory but fore >> some reason it refuses to compile for GENERIC mode. Anyone who got a >> clue why? Is it broken by default. > > > I cannot give any advice to you unless you tell me how it > fails... Right now I think its because I got an "old" kernel without FB support but tried to compile it in anyway. I'll wait for a new kernel. > > > >> Q6: Are there any specific switches that should / shouldn't be used when >> compiling the kernel to the DC. I thought of making a special "class" >> fro the DC in the compiler script. Is this a good idea? > > > Agreed. I've already added CONFIG_SH_DREAMCAST configuration to > the kernel. Great, it make life a lot easyer for newbies. >> Q8: How far has the Debian GNU/Linux Distribution come? As I understand >> It its just n it infancy, and where is the help most needed? > > > It depends on how long time it takes that GNU toolchain and > glibc for SuperH get stable, I think. Currently Niibe and kaz > are working on it. I really appreciate that. > Ah the missing link, glibc. But arn't ther some .deb packeges on m17n ? They moved to old last week. Is it becouse there is a larger upgrade going on? /Rene |