photon on sh7750 / tahoe

Hi –

I’m attempting to bring up all the supported devices on a Hitachi SH7750
with Tahoe IO card. This particular version sports an MQ200 graphics
controller - which is supported - but alas, I can’t even get io-graphics to
run!

I always get the error “dlopen(“gri-photon.so”) failed: Library cannot be
found” when I attempt to run io-graphics (with or without cmd line
parameters). The weird thing is, when I objdump -x the shle io-graphics
binary, it doesn’t list gri-photon.so as required. Anyway, I stuck
gri-photon.so on the LD_LIBRARY_PATH and still no luck. What gives?

Also, anyone know the .conf or cmd-line settings for this driver
(devg-mq200.so) on this board? Is there a general place to go to find that
kinda stuff out or do you have to look at the specs for the hardware and
take a shot?

Thanks,
Jason

Jason Ahmad <jahmad@stanford.edu> wrote:

Hi –

I’m attempting to bring up all the supported devices on a Hitachi SH7750
with Tahoe IO card. This particular version sports an MQ200 graphics
controller - which is supported - but alas, I can’t even get io-graphics to
run!

The MQ200 is not supported on the this particular daughterboard.
It may be possible to get it to work, but it’s never been tested. I don’t
believe there are plans to support it either, since the MQ200 chip has
been end-of-lifed.

I always get the error “dlopen(“gri-photon.so”) failed: Library cannot be
found” when I attempt to run io-graphics (with or without cmd line
parameters). The weird thing is, when I objdump -x the shle io-graphics
binary, it doesn’t list gri-photon.so as required. Anyway, I stuck
gri-photon.so on the LD_LIBRARY_PATH and still no luck. What gives?

Also, anyone know the .conf or cmd-line settings for this driver
(devg-mq200.so) on this board? Is there a general place to go to find that
kinda stuff out or do you have to look at the specs for the hardware and
take a shot?

Generally the only information available on the .conf files is contained
within the files themselves. It is often necessary to have the hardware
specs at hand in order to understand the .conf file settings.

Dave

Ok, thanks for the clarification. Actually, on a more general note I’m
having the same sorts of problems detailed below attempting to configure the
audio. (That I know for a fact is supported.)

Basically, it looks like none of the libraries are getting loaded despite
the fact that the directories are clearly spec’d in LD_LIBRARY_PATH. Could
it be a permissions thing (set the libs in question to 777)? An owner thing?
I have the LD_LIBRARY_PATH set with things like /fs0p0/lib but fs0p0 needs
to get mounted at start up…maybe a problem?

the error I get is “LoadDll(): dlopen(“mpegaudio_noph.so”) failed (Library
cannot be found)”

Thanks,

Jason

“David Donohoe” <ddonohoe@qnx.com> wrote in message
news:<ai9kh0$ojf$1@nntp.qnx.com>…

Jason Ahmad <> jahmad@stanford.edu> > wrote:

Hi –



I’m attempting to bring up all the supported devices on a Hitachi SH7750

with Tahoe IO card. This particular version sports an MQ200 graphics

controller - which is supported - but alas, I can’t even get io-graphics
to



run!



The MQ200 is not supported on the this particular daughterboard.

It may be possible to get it to work, but it’s never been tested. I don’t

believe there are plans to support it either, since the MQ200 chip has

been end-of-lifed.



I always get the error “dlopen(“gri-photon.so”) failed: Library cannot
be



found” when I attempt to run io-graphics (with or without cmd line

parameters). The weird thing is, when I objdump -x the shle io-graphics

binary, it doesn’t list gri-photon.so as required. Anyway, I stuck

gri-photon.so on the LD_LIBRARY_PATH and still no luck. What gives?



Also, anyone know the .conf or cmd-line settings for this driver

(devg-mq200.so) on this board? Is there a general place to go to find
that



kinda stuff out or do you have to look at the specs for the hardware and

take a shot?



Generally the only information available on the .conf files is contained

within the files themselves. It is often necessary to have the hardware

specs at hand in order to understand the .conf file settings.



Dave