linuxdc-dev

[linuxdc-dev]GD-ROM: Got larger result

[Michael G. <mg...@ho...>]

"GD-ROM: Got larger result"

That's what I am getting when trying to boot off the gdrom.
And it stops after that, inspite the error aparently not being fatal:
disconnecting and reconnecting maple devices still registers.

Could it be because I don't have a /dev/gdrom device?
But I do have devfs and devfs mount on boot, so I figured it should
take care of that...

Anyway, how would I go about debuging it further?
I stared at the gdrom driver for a while, but I doesn't really
make much sense to me... 
Any help would be greatly appreciated,
Mag.

Re: [linuxdc-dev]GD-ROM: Got larger result

[Robert L. <rm...@te...>]

On Thu, 2001-12-13 at 22:05, Michael Grig wrote:
> "GD-ROM: Got larger result"
> 
> That's what I am getting when trying to boot off the gdrom.
> And it stops after that, inspite the error aparently not being fatal:
> disconnecting and reconnecting maple devices still registers.
> 
> Could it be because I don't have a /dev/gdrom device?
> But I do have devfs and devfs mount on boot, so I figured it should
> take care of that...
> 
> Anyway, how would I go about debuging it further?
> I stared at the gdrom driver for a while, but I doesn't really
> make much sense to me... 

I've seen this error, same situation as you, and for the life of me I
can _not_ remember what I did to fix it. :-/

I did end up adding boot support for the gdrom, though, so that is the
first step.  If you aren't using a recent (past week or so) CVS dump,
apply the attached patch.

Make sure ISO-9660 fs support is compiled into your kernel.

Make sure you pass `root=/dev/gdrom ro' to the kernel command-line.

Having /dev/gdrom exist doesn't actually matter, the devices are looked
up in a table and have nothing to do with /dev or devfs.

See where this leads us ...

	Robert Love

[linuxdc-dev]Problem with porting SoX

[Adrian M. <ad...@mc...>]

I have been attempting to port SoX - a sound application (see 
http://sox.sourceforge.net).

After a bit of poking about I have got an application that runs, sortof, but 
when I try - for instance - ./sox imagination.wav -t ossdsp /dev/dsp - it 
reports (on the DC obviously) ---

<Walking through AICA device list>
<Attempting to lock chnnel 0>
./sox: Killing process "sox" due to unaligned access
<Walking through AICA device list>
Segmentation fault


[Messages enclosed <thus> are printk's from the driver - they indicated that 
the driver has not misbehaved (probably)]

To be honest I still don't know enough about Linux development to know what 
"unaligned access" is other than it sounds like a linker fix up problem. Is 
this the sort of problem that I should expect because of bugs in the tool 
chain, or it is because of some error I may have made?

All answers, guesses or otherwise, eagerly awaited - if anybody wants the app 
I can email it or post it on my web page - just let me know. (Without a 
/dev/dsp it is obviously gonna fail though!)


Adrian

Re: [linuxdc-dev]Problem with porting SoX

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

* Adrian McMenamin <ad...@mc...> on Sat, Dec 15, 2001:

>=20
> To be honest I still don't know enough about Linux development to know wh=
at=20
> "unaligned access" is other than it sounds like a linker fix up problem. =
Is=20
> this the sort of problem that I should expect because of bugs in the tool=
=20
> chain, or it is because of some error I may have made?
>=20

The SH4 expects all 16-bit accesses on 16-bit boundaries, and all 32-bit
accesses on 32-bit boundaries.  Check and make sure your driver is
accessing RAM, registers, whatever like it's supposed to.  Not a linker
issues, and it's a possibility that it's a toolchain bug - given
the quality of GCC's SH backend, you can't rule that out.  It's also
possible that sox does unaligned accesses, so don't rule that out either.

Start with your driver first.  View the assembler output via gcc -s,
(kbuild 2.5 is useful in this regard).

M. R.

Re: [linuxdc-dev]Problem with porting SoX

[Adrian M. <ad...@mc...>]

On Saturday 15 Dec 2001 8:05 pm, M. R. Brown wrote:

> Start with your driver first.  View the assembler output via gcc -s,
> (kbuild 2.5 is useful in this regard).
>
> M. R.

Okay, I will, but I doubt it's the driver (famous last words) as the command 
was just a fancy way of playing a .wav and I have no problems with that using 
the cat imagination.wav > /dev/dsp method, but thanks for the tip anyway.

Re: [linuxdc-dev]Problem with porting SoX

[Adrian M. <ad...@mc...>]

On Saturday 15 Dec 2001 8:15 pm, Adrian McMenamin wrote:
> On Saturday 15 Dec 2001 8:05 pm, M. R. Brown wrote:
> > Start with your driver first.  View the assembler output via gcc -s,
> > (kbuild 2.5 is useful in this regard).
> >
> > M. R.
>
> Okay, I will, but I doubt it's the driver (famous last words) as the
> command was just a fancy way of playing a .wav and I have no problems with
> that using the cat imagination.wav > /dev/dsp method, but thanks for the
> tip anyway.
>

For anyone who is interested, this (SoX) now works (most of the time). Hacked 
up makefiles etc, available from me on request.