SMC2 causes failure?

SMC2 causes failure?

[Gessner, Matt]

Howdy...
I'm experimenting getting SMC2 up and running as my console.
Interestingly enough, when the machine boots, it gets locked
into a page fault loop.
Has anyone else experienced this?  Has it been solved
elsewhere?
I'm using the most simple form of the SMC's, configured on
port B.

Regards,

Matt

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: SMC2 causes failure?

[Dan Malek]

Gessner, Matt wrote:

> I'm experimenting getting SMC2 up and running as my console.


The SMC2 isn't a very good choice for a console if you intend to use
it beyond some simple boot up messages.  It is one of the first
peripherals confiscated by other CPM functions, either by the assignment
of the I/O pins to some other use or the use of the parameter ram.

> Interestingly enough, when the machine boots, it gets locked
> into a page fault loop.

Are you loading a microcode relocation patch (or was one loaded and not
removed properly) without proper driver modifications?

Since the console is the first thing used by the kernel in the IMMR space,
do you have that mapped properly?


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

libraryopt

[Jon-Erling Dahl]

Hi,

I'm having problems getting libraryopt doing something.
(http://libraryopt.sourceforge.net)
Is there anybody out there that have used this utility
successfully?

I have created one directory under target/usr/lib/optinfo
containing a path, index and build file. However, it doesn't
seem to get run. Enabling the debug output, it resolvs a
lot of libraries, but the build file is never executed.

Any ideas?

Thanks,
jon-erling

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: libraryopt

[Michael Habermann]

At 01:24 PM 2/28/2002 +0100, Jon-Erling Dahl wrote:
>I'm having problems getting libraryopt doing something.
>(http://libraryopt.sourceforge.net)
>Is there anybody out there that have used this utility
>successfully?

There was a thread about this topic, with detailed descriptions. Maybe this
link helps you:
http://lists.linuxppc.org/linuxppc-embedded/200110/msg00156.html

I have not managed to use libraryopt (I tried not very hard), but was
successful with mklibs.sh.
If you are using hardhat linux, libraryopt is recommended.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: libraryopt

[Jon-Erling Dahl]

> >I'm having problems getting libraryopt doing something.
> >(http://libraryopt.sourceforge.net)
> >Is there anybody out there that have used this utility
> >successfully?
>
> There was a thread about this topic, with detailed descriptions.
> Maybe this
> link helps you:
> http://lists.linuxppc.org/linuxppc-embedded/200110/msg00156.html
>
> I have not managed to use libraryopt (I tried not very hard), but was
> successful with mklibs.sh.
> If you are using hardhat linux, libraryopt is recommended.

I managed to get it working. The libopt program seems to look
for the build script in the wrong directory (at least according
to my setup ;). Changing that, and the build script executed.

However, the build script is supposed to get all needed object
files as input. My build script didn't get any object files at
all and I think its because of this:

I have an application 'myapp' that depends on a shared library
'mylib'. 'mylib' in turn depends on 'somelib', like this:

myapp -> mylib -> somelib -> libc, libstdc++, etc

What I tried was to create an optimizer for somelib. But since
myapp doesn't depend on somelib directly, it seems that libopt
doesn't think any of the object files in 'somelib' is needed,
and hence no object files as input to the build script.
Is this correct? Does libopt only work when an application is
linked directly against the lib you're trying to optimize?
Am I completely missing something here?
I built an optimizer for 'mylib', and it worked correctly...

Are there any other utilities for solving this problem? Does
mklibs.sh solve it better?

Regards,
Jon-Erling

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: libraryopt

[Mark Hatle]

Jon-Erling Dahl wrote:
> files as input. My build script didn't get any object files at
> all and I think its because of this:
>
> I have an application 'myapp' that depends on a shared library
> 'mylib'. 'mylib' in turn depends on 'somelib', like this:
>
> myapp -> mylib -> somelib -> libc, libstdc++, etc
>
> What I tried was to create an optimizer for somelib. But since
> myapp doesn't depend on somelib directly, it seems that libopt
> doesn't think any of the object files in 'somelib' is needed,
> and hence no object files as input to the build script.
> Is this correct? Does libopt only work when an application is
> linked directly against the lib you're trying to optimize?
> Am I completely missing something here?
> I built an optimizer for 'mylib', and it worked correctly...

How did you link your app and the various libraries involved?  If you
used ld and did not specify the required libs, then the information
would not have gotten embedded into the elf information for each
required object.  If the elf information isn't there (or correct) the
library optimizer will be unable to correctly discover the link chain.
(You can use ldd or cross-ldd w/ hardhat linux to identify the required
libraries as listed in the elf information.)

When building software you should always use gcc to both compile and
link the software.  That is the only way to ensure that you get proper
library information, especially libc and libstdc++.  (In most cases you
can just replace ld w/ gcc, but for some apps you may have to throw in
some special gcc options.)

--Mark

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: libraryopt

[Jon-Erling Dahl]

<snip>

> How did you link your app and the various libraries involved?  If you
> used ld and did not specify the required libs, then the information
> would not have gotten embedded into the elf information for each
> required object.  If the elf information isn't there (or correct) the
> library optimizer will be unable to correctly discover the link chain.
> (You can use ldd or cross-ldd w/ hardhat linux to identify the required
> libraries as listed in the elf information.)

Thanks a lot. Had missed a -lsomelib in one of my Makefiles.
Works like a charm.

Regards,
Jon-Erling

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/