F19 Alpha RC5 compose

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

there is a Release Candidate compose for Alpha at
http://armpkgs.fedoraproject.org/mash/stage/19-Alpha-RC5/

there is a install tree as well as a image, the image is a minimal
install. it has all 3 kernels installed, kernel, kernel-lpae, and
kernel-tegra. to install to a sdcard run xzcat <image> > <sdcard> it
does not have boot.scr setup

as an example to boot on a trimslice you would put something like

setenv bootargs cma=64M root=LABEL=_/ ro rhgb console=ttyS0,115200
ext2load mmc 0:1 5880000 vmlinuz-3.9.0-301.fc19.armv7hl.tegra
ext2load mmc 0:1 4080000 uImage-3.9.0-301.fc19.armv7hl.tegra
ext2load mmc 0:1 4000000
dtb-3.9.0-301.fc19.armv7hl.tegra/tegra20-trimslice.dtb
bootz 4080000 5880000 4000000

in a boot.scr.in file in the first partition then run "mkimage -A arm
- -O linux -a 0 -e 0 -T script -C none -n "Fedora Boot Script" -d
boot.scr.in boot.scr"

i have tested it on a trimslice

Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
>
> iEYEARECAAYFAlGMFOcACgkQkSxm47BaWfe70gCfRrNaSPcnwNmI4MxrKAw9tvxo
> TZYAoMKmJe/nZzBeSM3L3gyaS8POBKu6
> =uxxv
> -----END PGP SIGNATURE-----

[Dennis Gilmore]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

El Thu, 9 May 2013 16:28:02 -0500
Dennis Gilmore  escribió:
> Hi all,
>
> there is a Release Candidate compose for Alpha at
> http://armpkgs.fedoraproject.org/mash/stage/19-Alpha-RC5/

some follow up, chrony is not installed so time may be off,  root's
password is empty. right now initial-setup is not running so you need
to log in at a console and setup a passwd for root and create user
accounts.

Dennis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
>
> iEYEARECAAYFAlGMGjMACgkQkSxm47BaWffJ0ACcDSkg5gVSzHcrk+vXBTi84zhC
> xl4An2AunF58PuTgktRiIsinE6P+qIa3
> =nPL6
> -----END PGP SIGNATURE-----

[Brendan Conoboy]

On 05/09/2013 02:28 PM, Dennis Gilmore wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> there is a Release Candidate compose for Alpha at
> http://armpkgs.fedoraproject.org/mash/stage/19-Alpha-RC5/

I've tested arm-boot-config with this image and it boots fine with it on 
trimslice.  There is one bug to be resolved that will prevent it working 
perfectly with anything but tegra.  Currently it will boot with the last 
kernel installed, even if it's a platform mismatch.  The last kernel 
installed was tegra so it works in this case, but that's hardly 
reliable.  I'll have an update shortly.  Trimslice users might give it a 
try anyhow:

http://people.fedoraproject.org/~blc/fedora-arm/arm-boot-config/

[d.marlin]

On 05/09/2013 04:28 PM, Dennis Gilmore wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> there is a Release Candidate compose for Alpha at
> http://armpkgs.fedoraproject.org/mash/stage/19-Alpha-RC5/
>
> there is a install tree as well as a image, the image is a minimal
> install. it has all 3 kernels installed, kernel, kernel-lpae, and
> kernel-tegra. to install to a sdcard run xzcat <image> > <sdcard> it
> does not have boot.scr setup
>
> as an example to boot on a trimslice you would put something like
>
> setenv bootargs cma=64M root=LABEL=_/ ro rhgb console=ttyS0,115200
> ext2load mmc 0:1 5880000 vmlinuz-3.9.0-301.fc19.armv7hl.tegra
> ext2load mmc 0:1 4080000 uImage-3.9.0-301.fc19.armv7hl.tegra
> ext2load mmc 0:1 4000000
> dtb-3.9.0-301.fc19.armv7hl.tegra/tegra20-trimslice.dtb
> bootz 4080000 5880000 4000000
>
> in a boot.scr.in file in the first partition then run "mkimage -A arm
> -O linux -a 0 -e 0 -T script -C none -n "Fedora Boot Script" -d
>
> boot.scr.in boot.scr"
>
> i have tested it on a trimslice

Is there any special U-Boot version requirement for Trim Slice, and if 
so, what version(s)?

Also, will this image work for OMAP, and if so, are there any special 
instructions for Panda?

d.marlin
========
> Dennis
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.19 (GNU/Linux)
>
> iEYEARECAAYFAlGMFOcACgkQkSxm47BaWfe70gCfRrNaSPcnwNmI4MxrKAw9tvxo
> TZYAoMKmJe/nZzBeSM3L3gyaS8POBKu6
> =uxxv
> -----END PGP SIGNATURE-----
> _______________________________________________
> arm mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/arm

[Peter Robinson]

On Fri, May 10, 2013 at 5:08 AM, David A. Marlin  wrote:
> On 05/09/2013 04:28 PM, Dennis Gilmore wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi all,
> >
> > there is a Release Candidate compose for Alpha at
> > http://armpkgs.fedoraproject.org/mash/stage/19-Alpha-RC5/
> >
> > there is a install tree as well as a image, the image is a minimal
> > install. it has all 3 kernels installed, kernel, kernel-lpae, and
> > kernel-tegra. to install to a sdcard run xzcat <image> > <sdcard> it
> > does not have boot.scr setup
> >
> > as an example to boot on a trimslice you would put something like
> >
> > setenv bootargs cma=64M root=LABEL=_/ ro rhgb console=ttyS0,115200
> > ext2load mmc 0:1 5880000 vmlinuz-3.9.0-301.fc19.armv7hl.tegra
> > ext2load mmc 0:1 4080000 uImage-3.9.0-301.fc19.armv7hl.tegra
> > ext2load mmc 0:1 4000000
> > dtb-3.9.0-301.fc19.armv7hl.tegra/tegra20-trimslice.dtb
> > bootz 4080000 5880000 4000000
> >
> > in a boot.scr.in file in the first partition then run "mkimage -A arm
> > -O linux -a 0 -e 0 -T script -C none -n "Fedora Boot Script" -d
> >
> > boot.scr.in boot.scr"
> >
> > i have tested it on a trimslice
>
> Is there any special U-Boot version requirement for Trim Slice, and if so,
> what version(s)?

The version with DTB as has been the case for all kernels 3.7+
> Also, will this image work for OMAP, and if so, are there any special
> instructions for Panda?

Not sure that it has the vfat partition so likely not.

Peter

[Brendan Conoboy]

On 05/09/2013 09:08 PM, David A. Marlin wrote:
> Is there any special U-Boot version requirement for Trim Slice, and if
> so, what version(s)?

It requires one of the 2012 uboots which include dtb support.  Works 
fine with the 1GB firmware as long as those extra environment variables 
are set.  Coincidentally, Compulab tells me there will be a -3 release 
which resolves the need to set those variables, sometime in June.
> Also, will this image work for OMAP, and if so, are there any special
> instructions for Panda?

The image I saw doesn't have a vfat partition 1, so without a great deal 
of manual intervention it would not work on OMAP.

[d.marlin]

On 05/10/2013 10:51 AM, Brendan Conoboy wrote:
> On 05/09/2013 09:08 PM, David A. Marlin wrote:
> > Is there any special U-Boot version requirement for Trim Slice, and if
> > so, what version(s)?
>
> It requires one of the 2012 uboots which include dtb support. Works 
> fine with the 1GB firmware as long as those extra environment 
> variables are set.

Thank you.
> Coincidentally, Compulab tells me there will be a -3 release which 
> resolves the need to set those variables, sometime in June.

Any chance of getting a 'preview release' for testing?
> > Also, will this image work for OMAP, and if so, are there any special
> > instructions for Panda?
>
> The image I saw doesn't have a vfat partition 1, so without a great 
> deal of manual intervention it would not work on OMAP.

So what are the 'blocker' images on F19?  For F18 it was vexpress, 
highbank, and panda.  Is it now just vexpress and highbank?

d.marlin
========

[Brendan Conoboy]

On 05/10/2013 09:22 AM, David A. Marlin wrote:
> Any chance of getting a 'preview release' for testing?

Don't know what else is planned.  Their uboot source tree is publicly 
available if anybody wants to go investigate though.

http://www.trimslice.com/wiki/index.php/Trim-Slice_U-Boot_Development
> So what are the 'blocker' images on F19?  For F18 it was vexpress,
> highbank, and panda.  Is it now just vexpress and highbank?

Does not appear to be documented on 
http://fedoraproject.org/wiki/Architectures/ARM/F19_Alpha_Release_Criteria 
so I'm not sure.  I believe we minimally need something with graphics 
support.  Perhaps we can take this RC5 compose and figure out what is 
working.