ppcboot and powerpc branch question

ppcboot and powerpc branch question

[fabien]

hi all,

After some problem with my custom board and kernel 2.6.19 about the
init process, i've moved
on 2.6.23 and that had fixed my problems. (related to this post :
http://marc.info/?l=linuxppc-embedded&m=119609022221017&w=2)
Apparently it was a problem with cpm_uart on SMC1.
(http://lkml.org/lkml/2007/9/23/99)
the patch have been integrated in 2.6.23. Now i use this kernel and
busybox works.
I want to migrated my board in powerpc branch instead of ppc (i plan
to use xenomai but in 2.6.23
there is only an adeos patch for piowerpc branch), but i see the use
of a device tree
instead of bd_t struct. I'm a bit disappointed because i also see that
older u-boot (in my case
ppcboot 1.1.5) aren't capable to pass dts to kernel.
Is there a way to keep my old bootloader to boot a powerpc branch kernel ?

Best regards
Fab

Re: ppcboot and powerpc branch question

[Grant Likely]

On 11/30/07, fabien <fabien.fb@gmail.com> wrote:
> hi all,
>
> After some problem with my custom board and kernel 2.6.19 about the
> init process, i've moved
> on 2.6.23 and that had fixed my problems. (related to this post :
> http://marc.info/?l=linuxppc-embedded&m=119609022221017&w=2)
> Apparently it was a problem with cpm_uart on SMC1.
> (http://lkml.org/lkml/2007/9/23/99)
> the patch have been integrated in 2.6.23. Now i use this kernel and
> busybox works.
> I want to migrated my board in powerpc branch instead of ppc (i plan
> to use xenomai but in 2.6.23
> there is only an adeos patch for piowerpc branch), but i see the use
> of a device tree
> instead of bd_t struct. I'm a bit disappointed because i also see that
> older u-boot (in my case
> ppcboot 1.1.5) aren't capable to pass dts to kernel.
> Is there a way to keep my old bootloader to boot a powerpc branch kernel ?

Yes, you can build a 'cuImage' in arch/powerpc which wraps the kernel
image with a device tree and copies the bd_t data into the tree before
booting.

Cheers,
g.


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

Re: ppcboot and powerpc branch question

[fabien]

2007/11/30, Grant Likely <grant.likely@secretlab.ca>:
> On 11/30/07, fabien <fabien.fb@gmail.com> wrote:
> > hi all,
> >
> > After some problem with my custom board and kernel 2.6.19 about the
> > init process, i've moved
> > on 2.6.23 and that had fixed my problems. (related to this post :
> > http://marc.info/?l=linuxppc-embedded&m=119609022221017&w=2)
> > Apparently it was a problem with cpm_uart on SMC1.
> > (http://lkml.org/lkml/2007/9/23/99)
> > the patch have been integrated in 2.6.23. Now i use this kernel and
> > busybox works.
> > I want to migrated my board in powerpc branch instead of ppc (i plan
> > to use xenomai but in 2.6.23
> > there is only an adeos patch for piowerpc branch), but i see the use
> > of a device tree
> > instead of bd_t struct. I'm a bit disappointed because i also see that
> > older u-boot (in my case
> > ppcboot 1.1.5) aren't capable to pass dts to kernel.
> > Is there a way to keep my old bootloader to boot a powerpc branch kernel ?
>
> Yes, you can build a 'cuImage' in arch/powerpc which wraps the kernel
> image with a device tree and copies the bd_t data into the tree before
> booting.
>
> Cheers,
> g.
>
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> grant.likely@secretlab.ca
> (403) 399-0195
>

Ok, thanks
So do I need to define a dts file or the bd_t struct only will be
sufficient to boot with cuImage ?
Best regards
Fab

Re: ppcboot and powerpc branch question

[Scott Wood]

fabien wrote:
> Ok, thanks
> So do I need to define a dts file or the bd_t struct only will be
> sufficient to boot with cuImage ?

You need to define a dts file (see the existing ones in 
arch/powerpc/boot/dts for examples), and set CONFIG_DEVICE_TREE to tell 
the wrapper which one to include.

Note that this dts must have linux,network-index properties in the 
network nodes for the MAC addresses to be filled in, and must have 
/chosen/linux,stdout-path if you want output from the wrapper (useful if 
something goes wrong (such as insufficient memory to relocate the 
kernel) or if you want to edit the command line).

You also need to do make zImage rather than make uImage for cuImage to 
be built.

-Scott

Re: ppcboot and powerpc branch question

[Clemens Koller]

fabien schrieb:
> hi all,
> 
> After some problem with my custom board and kernel 2.6.19 about the
> init process, i've moved
> on 2.6.23 and that had fixed my problems. (related to this post :
> http://marc.info/?l=linuxppc-embedded&m=119609022221017&w=2)
> Apparently it was a problem with cpm_uart on SMC1.
> (http://lkml.org/lkml/2007/9/23/99)
> the patch have been integrated in 2.6.23. Now i use this kernel and
> busybox works.
> I want to migrated my board in powerpc branch instead of ppc (i plan
> to use xenomai but in 2.6.23
> there is only an adeos patch for piowerpc branch), but i see the use
> of a device tree
> instead of bd_t struct. I'm a bit disappointed because i also see that
> older u-boot (in my case
> ppcboot 1.1.5) aren't capable to pass dts to kernel.
> Is there a way to keep my old bootloader to boot a powerpc branch kernel ?

please read linux/Documentation/powerpc/booting-without-of.txt

To get a cuImage, you
- need to adjust your <platform>.dts and configure your kernel to use it.
- need the latest dtc (device tree compiler),
- need the latest mkimage (from the latest u-boot tree)
- and build your cuImage by building the target zImage (make zImage)
-> your cuImage then rests in i.e. arch/powerpc/boot/cuImage.<platform>

Aside of no good documentation, I ran into the problem that the
embedded device tree doesn't get updated by the bd_t struct properly
(the mac addresses) in the latest versions of the kernel. This might be
a bug or a configuration error on my side. I didn't check yet.
U-Boot with full device tree support will hopfully fix that, when it's
out.

Regards,

-- 
Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com

Re: ppcboot and powerpc branch question

[fabien]

Thanks for yours advices Scott and Clemens i'll read the docs given
Best regards

2007/11/30, Clemens Koller <clemens.koller@anagramm.de>:
> fabien schrieb:
> > hi all,
> >
> > After some problem with my custom board and kernel 2.6.19 about the
> > init process, i've moved
> > on 2.6.23 and that had fixed my problems. (related to this post :
> > http://marc.info/?l=3Dlinuxppc-embedded&m=3D119609022221017&w=3D2)
> > Apparently it was a problem with cpm_uart on SMC1.
> > (http://lkml.org/lkml/2007/9/23/99)
> > the patch have been integrated in 2.6.23. Now i use this kernel and
> > busybox works.
> > I want to migrated my board in powerpc branch instead of ppc (i plan
> > to use xenomai but in 2.6.23
> > there is only an adeos patch for piowerpc branch), but i see the use
> > of a device tree
> > instead of bd_t struct. I'm a bit disappointed because i also see that
> > older u-boot (in my case
> > ppcboot 1.1.5) aren't capable to pass dts to kernel.
> > Is there a way to keep my old bootloader to boot a powerpc branch kerne=
l ?
>
> please read linux/Documentation/powerpc/booting-without-of.txt
>
> To get a cuImage, you
> - need to adjust your <platform>.dts and configure your kernel to use it.
> - need the latest dtc (device tree compiler),
> - need the latest mkimage (from the latest u-boot tree)
> - and build your cuImage by building the target zImage (make zImage)
> -> your cuImage then rests in i.e. arch/powerpc/boot/cuImage.<platform>
>
> Aside of no good documentation, I ran into the problem that the
> embedded device tree doesn't get updated by the bd_t struct properly
> (the mac addresses) in the latest versions of the kernel. This might be
> a bug or a configuration error on my side. I didn't check yet.
> U-Boot with full device tree support will hopfully fix that, when it's
> out.
>
> Regards,
>
> --
> Clemens Koller
> __________________________________
> R&D Imaging Devices
> Anagramm GmbH
> Rupert-Mayer-Stra=DFe 45/1
> Linhof Werksgel=E4nde
> D-81379 M=FCnchen
> Tel.089-741518-50
> Fax 089-741518-19
> http://www.anagramm-technology.com
>
>

Re: ppcboot and powerpc branch question

[Wolfgang Denk]

In message <f8f856500711300533t3bad1c1dxb4ff137534acbccb@mail.gmail.com> you wrote:
> 
> instead of bd_t struct. I'm a bit disappointed because i also see that
> older u-boot (in my case
> ppcboot 1.1.5) aren't capable to pass dts to kernel.

PPCBoot was a in a distant  past  before  U-Boot.  Actually,  PPCBoot
1.1.5 is more than 5 and a half years old. You cannot really expect a
Neanderthal man to drive a space shuttle.

> Is there a way to keep my old bootloader to boot a powerpc branch kernel ?

No. Please use a current U-Boot (i. e. at least U-Boot 1.3.0).

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
As in certain cults it is possible to kill a process if you know  its
true name.                      -- Ken Thompson and Dennis M. Ritchie

RE: ppcboot and powerpc branch question

[Pagnotta, Chris]

Wolgang,

This question does pertain to the thread in question, but..

I am currently using your ELDK 4.1 Uclibc and have written various
scripts that allow it to be used with buildroot makefiles. Are you going
to releasing a newer version anytime soon?

Thanks,
Chris P.

-----Original Message-----
From: linuxppc-embedded-bounces+chris.pagnotta=3Dviasat.com@ozlabs.org
[mailto:linuxppc-embedded-bounces+chris.pagnotta=3Dviasat.com@ozlabs.org]=

On Behalf Of Wolfgang Denk
Sent: Friday, November 30, 2007 2:16 PM
To: fabien
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ppcboot and powerpc branch question

In message <f8f856500711300533t3bad1c1dxb4ff137534acbccb@mail.gmail.com>
you wrote:
>=20
> instead of bd_t struct. I'm a bit disappointed because i also see that
> older u-boot (in my case
> ppcboot 1.1.5) aren't capable to pass dts to kernel.

PPCBoot was a in a distant  past  before  U-Boot.  Actually,  PPCBoot
1.1.5 is more than 5 and a half years old. You cannot really expect a
Neanderthal man to drive a space shuttle.

> Is there a way to keep my old bootloader to boot a powerpc branch
kernel ?

No. Please use a current U-Boot (i. e. at least U-Boot 1.3.0).

Best regards,

Wolfgang Denk

--=20
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
As in certain cults it is possible to kill a process if you know  its
true name.                      -- Ken Thompson and Dennis M. Ritchie
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded

Cannot login via tinylogin on sequoia

[Leonid]

Hi:

I have built u-boot, kernel and filesystem using ELDK 4.1 for AMCC
PPC440EPx sequoia board. When I boot linux using NFS filesystem,
supplied with ELDK itself, I can login (usrr root, no password). However
I couldn't login while used ramdisk, built by myself or taken from AMCC
resource CD. Combinations root/root or root/nothing don't work.=20

Sequoia login: root
Password:
Login incorrect

Please press Enter to activate this console. Dec 31 18:00:26 Sequoia
auth.warn login[37]: invalid password for `UNKNOWN' on `ttyS0'
Dec 31 18:00:26 Sequoia daemon.info init: Process '/bin/tinylogin login
-f root' (pid 37) exited.  Scheduling it for restart.

How I can learn what user/password combination are configured and how do
I change them? This is static/etc/passwd from my SIMPLE filesystem:

root::0:0:root:/root:/bin/sh
bin:*:1:1:bin:/bin:
daemon:*:2:2:daemon:/sbin:
halt:*:7:0:halt:/sbin:/sbin/halt
ftp:*:14:50:FTP User:/
nobody:*:99:99:Nobody:/:
target:$1$x4Rc1j78$n5FVlLwarSyMYoZaMlijU1:200:100:Test
User:/home:/bin/sh

Thanks,

Leonid.

Re: ppcboot and powerpc branch question

[Wolfgang Denk]

Dear Chris,

in message <821B2170E9E7F04FA38DF7EC21DE48710BA65802@VCAEXCH01.hq.corp.viasat.com> you wrote:
> 
> I am currently using your ELDK 4.1 Uclibc and have written various
> scripts that allow it to be used with buildroot makefiles. Are you going
> to releasing a newer version anytime soon?

Yes, we just showed ELDK 4.2 at the SPS/IPC/Drives trade show in
Nuremberg. OK, it's still beta since we wait for the final release of
Xenomai 2.4, but PPC and PPC64 beta is available for testers.

> -----Original Message-----
> From: linuxppc-embedded-bounces+chris.pagnotta=3Dviasat.com@ozlabs.org
> [mailto:linuxppc-embedded-bounces+chris.pagnotta=3Dviasat.com@ozlabs.org]=


Two remarks:
- Please don't top post / full quote. See
  http://www.netmeister.org/news/learn2quote.html
- Please post ELDK related requests on the ELDK mailing list, see
  http://lists.denx.de/mailman/listinfo/eldk

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
A good marriage would be between a blind wife and deaf husband.
                                               -- Michel de Montaigne

RE: Cannot login via tinylogin on sequoia

[Leonid]

I can avoid login procedure at all by replacing tinylogin call by simple
sh in inittab or by removing inittab at all:

#::askfirst:/bin/tinylogin login -f root=20
::askfirst:/bin/sh

I get shell prompt all right without logging. However login doesn't work
and I don't understand why.=20

I tried to change password using passwd (user: root, password: root),
but login still doesn't work:

/ # passwd root
Changing password for root
Enter the new password (minimum of 5, maximum of 8 characters) Please
use a combination of upper and lower case letters and numbers.
Enter new password:
Re-enter new password:
Password changed.
/ # Dec 31 18:02:29 Sequoia auth.info passwd[38]: password for `root'
changed by user `root'

/ # login

Sequoia login: root
Password:
Login incorrect

Does somebody know a way to make tinylogin give out more detailed
iunformation? Of course, I can always debug it since I have source...

Thanks,

Leonid.

-----Original Message-----
From: linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org
[mailto:linuxppc-embedded-bounces+leonid=3Da-k-a.net@ozlabs.org] On =
Behalf
Of Leonid
Sent: Friday, November 30, 2007 3:10 PM
To: linuxppc-embedded@ozlabs.org
Subject: Cannot login via tinylogin on sequoia

Hi:

I have built u-boot, kernel and filesystem using ELDK 4.1 for AMCC
PPC440EPx sequoia board. When I boot linux using NFS filesystem,
supplied with ELDK itself, I can login (usrr root, no password). However
I couldn't login while used ramdisk, built by myself or taken from AMCC
resource CD. Combinations root/root or root/nothing don't work.=20

Sequoia login: root
Password:
Login incorrect

Please press Enter to activate this console. Dec 31 18:00:26 Sequoia
auth.warn login[37]: invalid password for `UNKNOWN' on `ttyS0'
Dec 31 18:00:26 Sequoia daemon.info init: Process '/bin/tinylogin login
-f root' (pid 37) exited.  Scheduling it for restart.

How I can learn what user/password combination are configured and how do
I change them? This is static/etc/passwd from my SIMPLE filesystem:

root::0:0:root:/root:/bin/sh
bin:*:1:1:bin:/bin:
daemon:*:2:2:daemon:/sbin:
halt:*:7:0:halt:/sbin:/sbin/halt
ftp:*:14:50:FTP User:/
nobody:*:99:99:Nobody:/:
target:$1$x4Rc1j78$n5FVlLwarSyMYoZaMlijU1:200:100:Test
User:/home:/bin/sh

Thanks,

Leonid.
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded