Menu
▾
▴
linuxdc-dev
|
From: Adrian M. <ad...@mc...> - 2001-09-10 22:59:08
|
The ftp site appears to be down and so I loaded the rpm for the tools package
... but it doesn't appear to work for me.
I am sure this is because of my settings, but I am not clever enough to know
how to set this right!
When I run...
make
CROSS_COMPILE=/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/
dep zImage
I get this sort of thing...
/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/gcc -D__KERNEL__
-I/home/Adrian/linux/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686 -c -o
init/main.o init/main.c
cc1: Invalid option `arch=i686'
In file included from /home/Adrian/linux/include/linux/wait.h:19,
from /home/Adrian/linux/include/linux/fs.h:12,
from /home/Adrian/linux/include/linux/capability.h:17,
from /home/Adrian/linux/include/linux/binfmts.h:5,
from /home/Adrian/linux/include/linux/sched.h:9,
from /home/Adrian/linux/include/linux/mm.h:4,
from /home/Adrian/linux/include/linux/slab.h:14,
from /home/Adrian/linux/include/linux/proc_fs.h:5,
from init/main.c:15:
/home/Adrian/linux/include/asm/processor.h: In function `set_in_cr4':
/home/Adrian/linux/include/asm/processor.h:198: unknown register name `ax' in
`asm'
/home/Adrian/linux/include/asm/processor.h: In function `clear_in_cr4':
/home/Adrian/linux/include/asm/processor.h:208: unknown register name `ax' in
`asm'
In file included from /home/Adrian/linux/include/asm/semaphore.h:39,
from /home/Adrian/linux/include/linux/fs.h:199,
from /home/Adrian/linux/include/linux/capability.h:17,
from /home/Adrian/linux/include/linux/binfmts.h:5,
from /home/Adrian/linux/include/linux/sched.h:9,
from /home/Adrian/linux/include/linux/mm.h:4,
from /home/Adrian/linux/include/linux/slab.h:14,
from /home/Adrian/linux/include/linux/proc_fs.h:5,
from init/main.c:15:
/home/Adrian/linux/include/asm/system.h: In function `__set_64bit':
/home/Adrian/linux/include/asm/system.h:147: unknown register name `dx' in
`asm'
/home/Adrian/linux/include/asm/system.h:147: unknown register name `ax' in
`asm'
In file included from /home/Adrian/linux/include/linux/rwsem.h:27,
from /home/Adrian/linux/include/asm/semaphore.h:42,
from /home/Adrian/linux/include/linux/fs.h:199,
from /home/Adrian/linux/include/linux/capability.h:17,
from /home/Adrian/linux/include/linux/binfmts.h:5,
from /home/Adrian/linux/include/linux/sched.h:9,
from /home/Adrian/linux/include/linux/mm.h:4,
from /home/Adrian/linux/include/linux/slab.h:14,
from /home/Adrian/linux/include/linux/proc_fs.h:5,
from init/main.c:15:
/home/Adrian/linux/include/asm/rwsem.h: In function `__up_write':
/home/Adrian/linux/include/asm/rwsem.h:177: unknown register name `edx' in
`asm'
In file included from /home/Adrian/linux/include/net/checksum.h:35,
from /home/Adrian/linux/include/linux/raid/md.h:34,
from init/main.c:24:
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:72:30: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:105:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:105:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:105:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:121:13: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:121:13: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:121:13: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:121:13: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:121:13: warning: multi-line string
literals are deprecated
In file included from /home/Adrian/linux/include/net/checksum.h:35,
from /home/Adrian/linux/include/linux/raid/md.h:34,
from init/main.c:24:
/home/Adrian/linux/include/asm/checksum.h: At top level:
/home/Adrian/linux/include/asm/checksum.h:159: warning: `struct in6_addr'
declared inside parameter list
/home/Adrian/linux/include/asm/checksum.h:159: warning: its scope is only
this definition or declaration, which is probably not what you
want./home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line
string literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line string
literals are deprecated
/home/Adrian/linux/include/asm/checksum.h:161:17: warning: multi-line string
literals are deprecated
init/main.c: In function `name_to_kdev_t':
/home/Adrian/linux/include/asm/string.h:131: inconsistent operand constraints
in an `asm'
/home/Adrian/linux/include/asm/string.h:190: inconsistent operand constraints
in an `asm'
/home/Adrian/linux/include/asm/string.h:131: inconsistent operand constraints
in an `asm'
init/main.c: In function `root_dev_setup':
/home/Adrian/linux/include/asm/string.h:485: inconsistent operand constraints
in an `asm'
/home/Adrian/linux/include/asm/string.h:131: inconsistent operand constraints
in an `asm'
init/main.c: In function `checksetup':
/home/Adrian/linux/include/asm/string.h:190: inconsistent operand constraints
in an `asm'
/home/Adrian/linux/include/asm/string.h:131: inconsistent operand constraints
in an `asm'
init/main.c: In function `parse_options':
/home/Adrian/linux/include/asm/string.h:154: inconsistent operand constraints
in an `asm'
/home/Adrian/linux/include/asm/string.h:154: inconsistent operand constraints
in an `asm'
/home/Adrian/linux/include/asm/string.h:154: inconsistent operand constraints
in an `asm'
/home/Adrian/linux/include/asm/string.h:154: inconsistent operand constraints
in an `asm'
/home/Adrian/linux/include/asm/string.h:154: inconsistent operand constraints
in an `asm'
/home/Adrian/linux/include/asm/string.h:131: inconsistent operand constraints
in an `asm'
/home/Adrian/linux/include/asm/string.h:154: inconsistent operand constraints
in an `asm'
init/main.c:603: confused by earlier errors, bailing out
{standard input}: Assembler messages:
{standard input}:66: Error: unknown opcode
{standard input}:70: Error: unknown opcode
{standard input}:148: Error: unknown opcode
{standard input}:149: Error: unknown opcode
{standard input}:150: Error: unknown opcode
{standard input}:172: Error: unknown opcode
{standard input}:173: Error: unknown opcode
{standard input}:174: Error: unknown opcode
{standard input}:185: Error: unknown opcode
{standard input}:186: Error: unknown opcode
{standard input}:187: Error: unknown opcode
{standard input}:188: Error: unknown opcode
{standard input}:189: Error: unknown opcode
{standard input}:190: Error: unknown opcode
{standard input}:191: Error: unknown opcode
{standard input}:192: Error: unknown opcode
{standard input}:193: Error: unknown opcode
{standard input}:277: Error: unknown opcode
{standard input}:277: Error: unknown opcode
{standard input}:277: Error: unknown opcode
{standard input}:277: Error: unknown opcode
{standard input}:1592: Error: unknown opcode
{standard input}:1697: Error: unknown opcode
{standard input}:1743: Error: unknown opcode
{standard input}:1772: Error: unknown opcode
{standard input}:1772: Error: unknown opcode
{standard input}:1773: Error: unknown opcode
{standard input}:1775: Error: unknown opcode
{standard input}:1776: Error: unknown opcode
{standard input}:1777: Error: unknown opcode
{standard input}:1778: Error: invalid operands for opcode
make: *** [init/main.o] Error 1
Eeeek! What's wrong???
|
|
From: M. R. B. <mr...@0x...> - 2001-09-11 02:54:30
|
* Adrian McMenamin <ad...@mc...> on Tue, Sep 11, 2001:
> The ftp site appears to be down and so I loaded the rpm for the tools package
> ... but it doesn't appear to work for me.
>
> I am sure this is because of my settings, but I am not clever enough to know
> how to set this right!
>
> When I run...
>
> make
> CROSS_COMPILE=/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/
> dep zImage
>
You forgot ARCH=sh in your make command.
> I get this sort of thing...
>
> /opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/gcc -D__KERNEL__
> -I/home/Adrian/linux/include -Wall -Wstrict-prototypes -O2
> -fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686 -c -o
> init/main.o init/main.c
> cc1: Invalid option `arch=i686'
> In file included from /home/Adrian/linux/include/linux/wait.h:19,
> from /home/Adrian/linux/include/linux/fs.h:12,
> from /home/Adrian/linux/include/linux/capability.h:17,
> from /home/Adrian/linux/include/linux/binfmts.h:5,
> from /home/Adrian/linux/include/linux/sched.h:9,
> from /home/Adrian/linux/include/linux/mm.h:4,
> from /home/Adrian/linux/include/linux/slab.h:14,
> from /home/Adrian/linux/include/linux/proc_fs.h:5,
> from init/main.c:15:
[snip]
> {standard input}:1776: Error: unknown opcode
> {standard input}:1777: Error: unknown opcode
> {standard input}:1778: Error: invalid operands for opcode
> make: *** [init/main.o] Error 1
>
>
> Eeeek! What's wrong???
>
Because you didn't specify ARCH=sh, you attempted to compile an i386
kernel with a sh4 compiler. Use that for *all* kernel targets, including
menuconfig.
And I hope you're using the latest kernel from LinuxSH CVS (should be at
least 2.4.10-pre6).
M. R.
|
|
From: Adrian M. <ad...@mc...> - 2001-09-11 07:49:54
|
On Tuesday 11 September 2001 3:54 am, M. R. Brown wrote:
> * Adrian McMenamin <ad...@mc...> on Tue, Sep 11, 2001:
> > The ftp site appears to be down and so I loaded the rpm for the tools
> > package ... but it doesn't appear to work for me.
> >
> > I am sure this is because of my settings, but I am not clever enough to
> > know how to set this right!
> >
> > When I run...
> >
> > make
> > CROSS_COMPILE=/opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bi
> >n/ dep zImage
>
> You forgot ARCH=sh in your make command.
>
> > I get this sort of thing...
> >
> > /opt/billgatliff/H-i686-pc-linux-gnu/sh4-linux/sh4-linux/bin/gcc
> > -D__KERNEL__ -I/home/Adrian/linux/include -Wall -Wstrict-prototypes -O2
> > -fomit-frame-pointer -fno-strict-aliasing -pipe -march=i686 -c -o
> > init/main.o init/main.c
> > cc1: Invalid option `arch=i686'
> > In file included from /home/Adrian/linux/include/linux/wait.h:19,
> > from /home/Adrian/linux/include/linux/fs.h:12,
> > from /home/Adrian/linux/include/linux/capability.h:17,
> > from /home/Adrian/linux/include/linux/binfmts.h:5,
> > from /home/Adrian/linux/include/linux/sched.h:9,
> > from /home/Adrian/linux/include/linux/mm.h:4,
> > from /home/Adrian/linux/include/linux/slab.h:14,
> > from /home/Adrian/linux/include/linux/proc_fs.h:5,
> > from init/main.c:15:
>
> [snip]
>
> > {standard input}:1776: Error: unknown opcode
> > {standard input}:1777: Error: unknown opcode
> > {standard input}:1778: Error: invalid operands for opcode
> > make: *** [init/main.o] Error 1
> >
> >
> > Eeeek! What's wrong???
>
> Because you didn't specify ARCH=sh, you attempted to compile an i386
> kernel with a sh4 compiler. Use that for *all* kernel targets, including
> menuconfig.
>
> And I hope you're using the latest kernel from LinuxSH CVS (should be at
> least 2.4.10-pre6).
>
I am using the latest stuff from the CVS, yes. Late last night I was able to
access the ftp site - so should I use the downloaded tools or the ones that
popped out of the RPM?
Not wishing to sound ungrateful for what is, after all, help offered
voluntarily. But if I am meant to add an extra command why isn't it mentioned
in the HOWTOs?
> M. R.
|
|
From: M. R. B. <mr...@0x...> - 2001-09-11 08:12:37
|
* Adrian McMenamin <ad...@mc...> on Tue, Sep 11, 2001: > > Not wishing to sound ungrateful for what is, after all, help offered > voluntarily. But if I am meant to add an extra command why isn't it mentioned > in the HOWTOs? > What extra command? What are you complaining about? Just add `ARCH=sh' and be done with it. I have updated the documentation per your "request" :P. M. R. |
|
From: Adrian M. <ad...@mc...> - 2001-10-05 00:56:07
|
I have successfully compiled and run this for linuxdc. It's bloated, but it works. |
|
From: Adrian M. <ad...@mc...> - 2001-10-06 14:06:13
|
On Friday 05 October 2001 1:39 am, Adrian McMenamin wrote: > I have successfully compiled and run this for linuxdc. It's bloated, but it > works. > > _______________________________________________ > Linuxdc-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxdc-dev This turns out to be not quite as good as I thought yesterday morning! Maybe someone here might be able to help.... All the compiled examples run - the screen flashes up lime green and the windows with widgets appear on them - together with a mouse pointer in the middle of the screen. But the apps won't accept any keyboard or mouse input (my mouse is a PS/2 through an adaptor, but it's a proper DC keyboard). Keystrokes just result in characters appearing at the bottom of the screen - though the app keeps running and writing to the framebuffer at the same time if that is required. (Ctrl+C will break the app). Any ideas? Is this a setup/config problem do you think? Or a problem with QtE? My hunch is the former, but I don't know. The only device nodes I have set up are /dev/console and /dev/fb0 - could that be it? Adrian |
|
From: M. R. B. <mr...@0x...> - 2001-10-06 16:00:05
|
* Adrian McMenamin <ad...@mc...> on Sat, Oct 06, 2001: > > The only device nodes I have set up are /dev/console and /dev/fb0 - could > that be it? > Yes, use the MAKEDEV script that I mailed you to create the proper device nodes. You at least want "MAKEDEV std" and "MAKEDEV input". Make a symlink from /dev/input/mice to /dev/psaux (yeah, but QtE expects /dev/psaux to be rw, I don't know why it doesn't use /dev/input/mice directly). Of course make sure all of the input core drivers are compiled into the kernel, as well as the Maple mouse and keyboard support. Note that these *cannot* be used as modules, do to a flaw in the Maple driver design. I'm able to run QtE static, I still can't do shared yet (gcc-3.0.1 issues), and I'm working on QPE at the moment. Then, konqueror is next :P. Note: Currently the best way to verify that your DC mouse, keyboard, and controller are working is to use the distro provided at m17n.org. With a bit of hacking, you can set this up as your NFSROOT, so you can just move apps their when your ready to test. It comes with all of the /dev nodes created (actually it uses devfs). Do *not* use the kernel supplied with that distro, as it's hopelessly out of date. Do compile IP autoconfiguration and NFS root support into your kernel. I've attached my /etc/fstab file. Here are my kernel command-line args: mem=16M video=pvr2fb:640x480-16 root=/dev/nfs \ nfsroot=192.168.1.11:/home/mrbrown/dcdev/nfs/nfsroot \ ip=192.168.1.21::192.168.1.254:255.255.255.0:blackbox::off Read linux/Documentation/nfsroot.txt for more info. M. R. |
|
From: Adrian M. <ad...@mc...> - 2001-10-06 23:57:24
|
On Saturday 06 October 2001 4:59 pm, M. R. Brown wrote: > * Adrian McMenamin <ad...@mc...> on Sat, Oct 06, 2001: > > The only device nodes I have set up are /dev/console and /dev/fb0 - could > > that be it? > > Yes, use the MAKEDEV script that I mailed you to create the proper device > nodes. You at least want "MAKEDEV std" and "MAKEDEV input". Make a > symlink from /dev/input/mice to /dev/psaux (yeah, but QtE expects > /dev/psaux to be rw, I don't know why it doesn't use /dev/input/mice > directly). > Thanks, problem now appears to be fixed. |
|
From: Adrian M. <ad...@mc...> - 2001-10-13 15:55:40
|
On Saturday 06 October 2001 4:59 pm, M. R. Brown wrote: > > Note: Currently the best way to verify that your DC mouse, keyboard, and > controller are working is to use the distro provided at m17n.org. With a > bit of hacking, you can set this up as your NFSROOT, so you can just move > apps their when your ready to test. It comes with all of the /dev nodes > created (actually it uses devfs). Do *not* use the kernel supplied with > that distro, as it's hopelessly out of date. Do compile IP > autoconfiguration and NFS root support into your kernel. I've attached my > /etc/fstab file. Here are my kernel command-line args: > > mem=16M video=pvr2fb:640x480-16 root=/dev/nfs \ > nfsroot=192.168.1.11:/home/mrbrown/dcdev/nfs/nfsroot \ > ip=192.168.1.21::192.168.1.254:255.255.255.0:blackbox::off > > Read linux/Documentation/nfsroot.txt for more info. > I have been able to successfully (?) set up my DC to mount an NFS partition as root (busybox), but the file system is only being mounted as readonly - which is next to useless. I can't spot any configuration error, maybe somebody here can. exports file on ix86 box... /home/Adrian/nfs/initrd dreamy(rw,no_root_squash) #Dreamcast shell kernel command line... commandline: .ascii "mem=16M video=pvr2fb root=/dev/nfs nfsroot=192.168.62.123:/home/Adrian/nfs/initrd ip=192.168.62.2:192.168.62.123::255.255.255.0:dreamy::rarp" .byte 0 .end I'm not using an /etc/fstab file on the DC at the moment - as it makes no difference whether I use one or not - it all still mounts as ro. Any help? Thanks Adrian |
|
From: <ga...@wi...> - 2001-10-13 16:29:39
|
On Sat, Oct 13, 2001 at 04:41:10PM +0100, Adrian McMenamin wrote: > I have been able to successfully (?) set up my DC to mount an NFS partition > as root (busybox), but the file system is only being mounted as readonly - > which is next to useless. I can't spot any configuration error, maybe > somebody here can. > I had this exactly same problem, it took me a a couple days to finally figure out what was happening. The NFS root was being mounted but then the way I had it setup the network interface was going and grabbing another IP address which caused the root to be remounted readonly. I disabled the network configuration in /etc/network/interfaces and then it worked fine. Gareth -- Gareth J. Greenaway ga...@wi... |
|
From: Adrian M. <ad...@mc...> - 2001-10-13 16:35:18
|
On Saturday 13 October 2001 5:29 pm, Gareth J. Greenaway wrote: > On Sat, Oct 13, 2001 at 04:41:10PM +0100, Adrian McMenamin wrote: > > I have been able to successfully (?) set up my DC to mount an NFS > > partition as root (busybox), but the file system is only being mounted as > > readonly - which is next to useless. I can't spot any configuration > > error, maybe somebody here can. > > I had this exactly same problem, it took me a a couple days to finally > figure out what was happening. The NFS root was being mounted but then > the way I had it setup the network interface was going and grabbing > another IP address which caused the root to be remounted readonly. I > disabled the network configuration in /etc/network/interfaces and then > it worked fine. > > > Gareth Sounds right - but I don't have an /etc/network/interfaces file to disable! The /etc directory on the DC's root partition is empty :-< Does this mean some jiggery-pokery with the kernel command line? |
|
From: M. R. B. <mr...@0x...> - 2001-10-13 18:11:40
|
* Adrian McMenamin <ad...@mc...> on Sat, Oct 13, 2001: > Sounds right - but I don't have an /etc/network/interfaces file to disabl= e!=20 > The /etc directory on the DC's root partition is empty :-< >=20 If you're using busybox as a base system, setup /etc/inittab and try remounting NFS rw from /etc/init.d/rcS, also setup an /etc/fstab with your NFS root entry. Also, I'm a bit confused about your kernel options, why use rarp if you're specifying an IP address? Here's my command-line: mem=3D16M video=3Dpvr2fb:640x480-16 root=3D/dev/nfs \ nfsroot=3D192.168.1.11:/home/mrbrown/dcdev/nfs/nfsroot \ ip=3D192.168.1.21::192.168.1.254:255.255.255.0:blackbox::off Notice that I've turned IP autoconfiguration off since I'm assigning a static IP to the DC. M. R. |
|
From: Adrian M. <ad...@mc...> - 2001-10-13 23:49:20
|
On Saturday 13 October 2001 7:11 pm, M. R. Brown wrote: > * Adrian McMenamin <ad...@mc...> on Sat, Oct 13, 2001: > > Sounds right - but I don't have an /etc/network/interfaces file to > > disable! The /etc directory on the DC's root partition is empty :-< > > If you're using busybox as a base system, setup /etc/inittab and try > remounting NFS rw from /etc/init.d/rcS, also setup an /etc/fstab with your > NFS root entry. > Thanks, this works - if you leave out the inittab step. Don't ask me why, but with /etc/inittab it fails - something to do with the fact that busybox appears to be running before inittab is processed, I'd guess. |
|
From: Danny R. <me...@op...> - 2001-10-14 05:14:09
|
Okay guys, it's been a while since I've worked on the LinuxDC project. I downloaded the updated CVS module linux-sh-dc, then copied the files into the 2.4.10 kernel codebase. I used the HOWTO's .config then added maple bus support in make menuconfig. Now nothing works as far as the HOWTO is concerned. I try doing $ make ARCH=sh CROSS_COMPILE=/usr/local/bin/sh-elf- dep zImage make[1]: Entering directory `/home/Danny/linux/arch/sh/boot' make[1]: Nothing to be done for `dep'. make[1]: Leaving directory `/home/Danny/linux/arch/sh/boot' scripts/mkdep -- init/*.c > .depend scripts/mkdep -- `find /home/Danny/linux/include/asm /home/Danny/linux/include/l inux /home/Danny/linux/include/scsi /home/Danny/linux/include/net -name SCCS -pr une -o -follow -name \*.h ! -name modversions.h -print` > .hdepend scripts/mkdep: error 22 make: *** [dep-files] Error 2 Am I missing steps? Also, the menuconfig has no mention of NFS support, or even network support/BBA for that matter. What happened to the old linux module? Also, I finally got a BBA, so no more burning CD's every 5 seconds. Do I simply use the load+exec feature of DC load on a kernel image? How does that work? Thanks guys, -Danny |
|
From: Paul M. <pm...@mv...> - 2001-10-14 05:29:36
|
On Sun, Oct 14, 2001 at 01:13:47AM -0400, Danny Rodriguez wrote: > Okay guys, it's been a while since I've worked on the LinuxDC project. I > downloaded the updated CVS module linux-sh-dc, then copied the files > into the 2.4.10 kernel codebase. >=20 linux-sh-dc is an _experimental_ CVS module. It's where all the new development that isn't fit for general consumption goes. All the stuff you'= re looking for is in the linuxsh CVS. See http://sf.net/projects/linuxsh/ > I used the HOWTO's .config then added maple bus support in make > menuconfig. Now nothing works as far as the HOWTO is concerned. I try > doing=20 >=20 HOWTO probably needs to be updated.. the maple stuff in the linux-sh-dc mod= ule is an experimental work-in-progress at a new implementation of the maple bus to behave somewhat more intelligently. If you're interested in functional, = you want the old maple stuff thats in the LinuxSH CVS. >=20 > Am I missing steps? Also, the menuconfig has no mention of NFS support, > or even network support/BBA for that matter. >=20 > What happened to the old linux module? >=20 Most of our changes got pushed into the LinuxSH CVS, and that's where all t= he "stable" stuff goes now. Experimental and new stuff goes in the LinuxDC CVS. Unless you're a kernel hacker interested in hacking on new things, stay away from the linux-sh-dc module. Regards, --=20 Paul Mundt <pm...@mv...> MontaVista Software, Inc. |
|
From: Danny R. <me...@op...> - 2001-10-14 06:21:45
|
Do you guys, by any chance, have sample .config files for the DC? One that supports the BBA and NFS? -Danny -----Original Message----- From: Paul Mundt [mailto:pm...@mv...] Sent: Sunday, October 14, 2001 1:30 AM To: Danny Rodriguez Cc: lin...@li... Subject: Re: [linuxdc-dev]Some basic questions and Linux DC + NFS On Sun, Oct 14, 2001 at 01:13:47AM -0400, Danny Rodriguez wrote: > Okay guys, it's been a while since I've worked on the LinuxDC project. I > downloaded the updated CVS module linux-sh-dc, then copied the files > into the 2.4.10 kernel codebase. > linux-sh-dc is an _experimental_ CVS module. It's where all the new development that isn't fit for general consumption goes. All the stuff you're looking for is in the linuxsh CVS. See http://sf.net/projects/linuxsh/ > I used the HOWTO's .config then added maple bus support in make > menuconfig. Now nothing works as far as the HOWTO is concerned. I try > doing > HOWTO probably needs to be updated.. the maple stuff in the linux-sh-dc module is an experimental work-in-progress at a new implementation of the maple bus to behave somewhat more intelligently. If you're interested in functional, you want the old maple stuff thats in the LinuxSH CVS. > > Am I missing steps? Also, the menuconfig has no mention of NFS support, > or even network support/BBA for that matter. > > What happened to the old linux module? > Most of our changes got pushed into the LinuxSH CVS, and that's where all the "stable" stuff goes now. Experimental and new stuff goes in the LinuxDC CVS. Unless you're a kernel hacker interested in hacking on new things, stay away from the linux-sh-dc module. Regards, -- Paul Mundt <pm...@mv...> MontaVista Software, Inc. |
|
From: Adrian M. <ad...@mc...> - 2001-10-14 10:02:49
|
I've sent mine direct to Danny, but should anyone want it - try http://www.mcmen.demon.co.uk/linuxdc/config ...and just a reminder that you'll find a BBA supporting (but not NFS booting elf'ed kernel at http://www.mcmen.demon.co.uk/linuxdc - and ther's also a compiled x86 copy of the dc-tool app there too. But no documentation for any of this! On Sunday 14 October 2001 7:21 am, Danny Rodriguez wrote: > Do you guys, by any chance, have sample .config files for the DC? One > that supports the BBA and NFS? > > -Danny > |
|
From: Danny R. <me...@op...> - 2001-10-14 14:54:02
|
Okay, I'm using Adrian's config with NFS enabled. But I'm getting the same errors as before. Steps taken : make ARCH=sh config with current .config file make ARCH=sh CROSS_COMPILE=sh-elf- (errors) I edited the Makefile to do ARCH=sh and CROSS_COMPILE=sh-elf- (which are in my path). When I do make dep, or make ARCH=sh CROSS_COMPILE=/usr/local/bin/sh-elf- dep (both are equivalent errors)... I get this : make[1]: Entering directory `/home/Danny/kernel/arch/sh/boot' make[1]: Nothing to be done for `dep'. make[1]: Leaving directory `/home/Danny/kernel/arch/sh/boot' scripts/mkdep -- init/*.c > .depend scripts/mkdep -- `find /home/Danny/kernel/include/asm /home/Danny/kernel/include /linux /home/Danny/kernel/include/scsi /home/Danny/kernel/include/net -name SCCS -prune -o -follow -name \*.h ! -name modversions.h -print` > .hdepend scripts/mkdep: error 22 make: *** [dep-files] Error 2 What am I missing here? Thanks! -Danny -----Original Message----- From: Adrian McMenamin [mailto:ad...@mc...] Sent: Sunday, October 14, 2001 6:04 AM To: Danny Rodriguez; 'Paul Mundt' Cc: lin...@li... Subject: Re: [linuxdc-dev]Some basic questions and Linux DC + NFS I've sent mine direct to Danny, but should anyone want it - try http://www.mcmen.demon.co.uk/linuxdc/config ...and just a reminder that you'll find a BBA supporting (but not NFS booting elf'ed kernel at http://www.mcmen.demon.co.uk/linuxdc - and ther's also a compiled x86 copy of the dc-tool app there too. But no documentation for any of this! On Sunday 14 October 2001 7:21 am, Danny Rodriguez wrote: > Do you guys, by any chance, have sample .config files for the DC? One > that supports the BBA and NFS? > > -Danny > |
|
From: M. R. B. <mr...@0x...> - 2001-10-14 16:58:47
|
* Danny Rodriguez <me...@op...> on Sun, Oct 14, 2001: > Okay, I'm using Adrian's config with NFS enabled. But I'm getting the > same errors as before. >=20 > Steps taken : >=20 > make ARCH=3Dsh config with current .config file > make ARCH=3Dsh CROSS_COMPILE=3Dsh-elf- > (errors) >=20 sh-elf? Are you kidding me? Read Bill Gatliff's Linux/Dreamcast article on LinuxDevices.com, and don't come back until you run into *real* problems. M. R. |
|
From: Danny R. <me...@op...> - 2001-10-14 17:48:17
|
I apologize for my idiocy. I just wasn't thinking. -Danny > -----Original Message----- > From: lin...@li... [mailto:linuxdc-dev- > ad...@li...] On Behalf Of M. R. Brown > Sent: Sunday, October 14, 2001 12:58 PM > To: Danny Rodriguez > Cc: ad...@mc...; 'Paul Mundt'; linuxdc- > de...@li... > Subject: Re: [linuxdc-dev]Some basic questions and Linux DC + NFS > > * Danny Rodriguez <me...@op...> on Sun, Oct 14, 2001: > > > Okay, I'm using Adrian's config with NFS enabled. But I'm getting the > > same errors as before. > > > > Steps taken : > > > > make ARCH=sh config with current .config file > > make ARCH=sh CROSS_COMPILE=sh-elf- > > (errors) > > > > sh-elf? Are you kidding me? > > Read Bill Gatliff's Linux/Dreamcast article on LinuxDevices.com, and don't > come back until you run into *real* problems. > > M. R. |
|
From: M. R. B. <mr...@0x...> - 2001-10-14 18:01:09
|
* Danny Rodriguez <me...@op...> on Sun, Oct 14, 2001: >=20 [...] Currently Bill's article [1] is the best guide to getting started, Karl and= I are working on the content of linuxdc.org (still down) as I write this. We'll be providing binaries of the tools at that point as well. I couldn't really forsee anyone having problems with Bill's article, since = he covers all of the bases and leaves no room for error :). If you do start getting into other problems (i.e. NFS mounting etc.) don't hesitate to ask about them here. [1] http://linuxdevices.com/articles/AT7466555948.html M. R. |
|
From: Adrian M. <ad...@mc...> - 2001-10-21 22:30:26
|
As promised on IRC I am making a few faltering steps towards creating a sound driver for the DC. I have started by compiling the sound_core.c written by Alan Cox. It compiles fine using sh4-linux-gcc but when I use modprobe to load it, I get "unresolved symbol mod_firmware_load". I can't find any explanation for this function/macro in the Linux Device Drivers book and while I can find lots of examples of other people having this problem with their sound cards/linux kernels when I trawl through Google, I get no clear explanation. Anyone here know what this is about? |
|
From: M. R. B. <mr...@0x...> - 2001-10-21 23:22:20
|
* Adrian McMenamin <ad...@mc...> on Sun, Oct 21, 2001: > As promised on IRC I am making a few faltering steps towards creating a s= ound=20 > driver for the DC. >=20 > I have started by compiling the sound_core.c written by Alan Cox. >=20 > It compiles fine using sh4-linux-gcc but when I use modprobe to load it, = I=20 > get "unresolved symbol mod_firmware_load". I can't find any explanation f= or=20 > this function/macro in the Linux Device Drivers book and while I can find= =20 > lots of examples of other people having this problem with their sound=20 > cards/linux kernels when I trawl through Google, I get no clear explanati= on. >=20 > Anyone here know what this is about? >=20 Since this sounds like more of a generic "full-scoping" kernel issue, you probably want to forward this to lkml. M. R. |
|
From: Adrian M. <ad...@mc...> - 2001-10-21 23:30:20
|
On Monday 22 October 2001 12:21 am, M. R. Brown wrote: > > Since this sounds like more of a generic "full-scoping" kernel issue, you > probably want to forward this to lkml. > > M. R. My own stupidity, I'm afraid. The answer was pretty obvious when I looked at the source code - I needed to compile another file alongside it which included the body of the missing function. Doh! Anyway, it's fixed now, it compiles and it loads. Of course, it doesn't actually do anything. It's just the place holder for the most basic of operations. |
|
From: Adrian M. <ad...@mc...> - 2001-10-26 00:05:13
|
1. Has anybody any experience of using DMA in the kernel - when I compile it in the keyboard gets disabled - has nobody written a device driver that uses DMA, for instance? 2. I am now using devfs but this breaks QtE (which appears to want to use /dev/fb0) and I can see no obvious way to alter QtE to fix it. Any thoughts anyone? Adrian |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X