On Sat, Jul 12, 2014 at 10:27:00AM +0100, Ian Campbell wrote:
> On Fri, 2014-07-11 at 16:33 -0700, Vagrant Cascadian wrote:
> > On Tue, Jul 08, 2014 at 08:03:30PM +0100, Ian Campbell wrote:
> > > I think the patch below resolves the worst issue and it works for me on
> > > cubietruck.
> > >
> > >
On Fri, 2014-07-11 at 16:33 -0700, Vagrant Cascadian wrote:
> Control: tags 751816 patch
>
> On Tue, Jul 08, 2014 at 08:03:30PM +0100, Ian Campbell wrote:
> > I think the patch below resolves the worst issue and it works for me on
> > cubietruck.
> >
> > The more minor stuff mentioned in that rep
Control: tags 751816 patch
On Tue, Jul 08, 2014 at 08:03:30PM +0100, Ian Campbell wrote:
> I think the patch below resolves the worst issue and it works for me on
> cubietruck.
>
> The more minor stuff mentioned in that report I'm not sure it is
> actually worth worrying over. The main one seems
On Mon, 2014-06-16 at 22:19 +0100, Ian Campbell wrote:
> On Mon, 2014-06-16 at 22:15 +0200, Karsten Merker wrote:
> > On Mon, Jun 16, 2014 at 08:08:51PM +0100, Ian Campbell wrote:
> > > On Sun, 2014-06-15 at 15:14 +0200, Karsten Merker wrote:
> > > > I am not sure that we should handle commandline
On Mon, 2014-06-30 at 16:09 -0500, Robert Nelson wrote:
> On Mon, Jun 30, 2014 at 3:59 PM, Ian Campbell wrote:
> > On Fri, 2014-06-20 at 22:07 -0700, Vagrant Cascadian wrote:
> >> > So the unambiguously preferable search order is "/boot /"; in some cases
> >> > this will give an extra directory lo
On Mon, Jun 30, 2014 at 3:59 PM, Ian Campbell wrote:
> On Fri, 2014-06-20 at 22:07 -0700, Vagrant Cascadian wrote:
>> > So the unambiguously preferable search order is "/boot /"; in some cases
>> > this will give an extra directory lookup,
>>
>> Well, four extra directory lookups (boot.scr, uEnv.t
On Fri, 2014-06-20 at 22:07 -0700, Vagrant Cascadian wrote:
> > So the unambiguously preferable search order is "/boot /"; in some cases
> > this will give an extra directory lookup,
>
> Well, four extra directory lookups (boot.scr, uEnv.txt, zImage, uImage)...
> though it could probably be writt
On Fri, Jun 20, 2014 at 09:34:05PM -0700, Steve Langasek wrote:
> On Thu, Jun 19, 2014 at 07:58:25AM -0700, Vagrant Cascadian wrote:
> > On Thu, Jun 19, 2014 at 04:11:13PM +0200, Rainer Dorsch wrote:
> > > On Sunday 15 June 2014 12:14:03 Vagrant Cascadian wrote:
> > > > So, either remove or move uI
On Thu, Jun 19, 2014 at 07:58:25AM -0700, Vagrant Cascadian wrote:
> On Thu, Jun 19, 2014 at 04:11:13PM +0200, Rainer Dorsch wrote:
> > Hi Vagrant,
> > On Sunday 15 June 2014 12:14:03 Vagrant Cascadian wrote:
> > > So, either remove or move uImage elsewhere, or change the search order to
> > > sea
On Thu, Jun 19, 2014 at 04:13:18PM +0200, Rainer Dorsch wrote:
> On Thursday 19 June 2014 16:01:48 Rainer Dorsch wrote:
> > The problem was caused by the existence of /uImage, I renamed that (and
> > /ramdisk) and the problem went away.
>
> BTW, I do not see anywhere a reference to /uImage in boo
On Thu, Jun 19, 2014 at 04:11:13PM +0200, Rainer Dorsch wrote:
> Hi Vagrant,
>
> On Sunday 15 June 2014 12:14:03 Vagrant Cascadian wrote:
> > So, either remove or move uImage elsewhere, or change the search order to
> > seach /boot first:
> >
> > setenv boot_prefixes /boot /
>
> Wouldn't that
On Thursday 19 June 2014 16:01:48 Rainer Dorsch wrote:
> The problem was caused by the existence of /uImage, I renamed that (and
> /ramdisk) and the problem went away.
BTW, I do not see anywhere a reference to /uImage in boot.scr. Does anybody
understand why u-boot is checking for u-boot?
Thank
Hi Vagrant,
On Sunday 15 June 2014 12:14:03 Vagrant Cascadian wrote:
> So, either remove or move uImage elsewhere, or change the search order to
> seach /boot first:
>
> setenv boot_prefixes /boot /
Wouldn't that be a good default, because the flash-kernel puts everything in
/boot and why hav
On Sunday 15 June 2014 12:14:03 Vagrant Cascadian wrote:
> Merging both replies into a single email here...
>
> On Sun, Jun 15, 2014 at 12:43:13PM +0200, Rainer Dorsch wrote:
> > On Sunday 15 June 2014 00:23:07 Vagrant Cascadian wrote:
> > > My hunch is loading your bootscript to an alternate addr
On Mon, 2014-06-16 at 22:15 +0200, Karsten Merker wrote:
> On Mon, Jun 16, 2014 at 08:08:51PM +0100, Ian Campbell wrote:
> > On Sun, 2014-06-15 at 15:14 +0200, Karsten Merker wrote:
> > > I am not sure that we should handle commandline parameters this way.
> >
> > Do we think the current shortcomi
On Sun, 2014-06-15 at 15:14 +0200, Karsten Merker wrote:
> I am not sure that we should handle commandline parameters this way.
Do we think the current shortcomings here are worth keeping flash-kernel
>3.19 out of Jessie for now? As it stands it will propagate on Wednesday
I think.
I'm in two min
On Sun, 2014-06-15 at 15:14 +0200, Karsten Merker wrote:
> On Sun, Jun 15, 2014 at 11:18:49AM +0100, Ian Campbell wrote:
> > On Sat, 2014-06-14 at 15:37 -0700, Vagrant Cascadian wrote:
>
> > > As I've been writing up a few bootscripts for flash-kernel lately, I've
> > > been
> > > wondering about
On Sun, 2014-06-15 at 11:18 +0100, Ian Campbell wrote:
> On Sat, 2014-06-14 at 15:37 -0700, Vagrant Cascadian wrote:
> > On Sat, Jun 14, 2014 at 11:56:01PM +0200, Karsten Merker wrote:
> > > On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> > > It looks like you might not have set a
Merging both replies into a single email here...
On Sun, Jun 15, 2014 at 12:43:13PM +0200, Rainer Dorsch wrote:
> On Sunday 15 June 2014 00:23:07 Vagrant Cascadian wrote:
> > My hunch is loading your bootscript to an alternate address is somehow
> > causing an issue...
> >
> > instead of specify
Hi Vagrant,
On Sunday 15 June 2014 00:23:07 Vagrant Cascadian wrote:
> On Sun, Jun 15, 2014 at 08:36:33AM +0200, Rainer Dorsch wrote:
> > On Saturday 14 June 2014 14:48:08 Vagrant Cascadian wrote:
> > > On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> > I use your original boot.scr
Hi Vagrant,
On Sunday 15 June 2014 00:23:07 Vagrant Cascadian wrote:
> On Sun, Jun 15, 2014 at 08:36:33AM +0200, Rainer Dorsch wrote:
> > On Saturday 14 June 2014 14:48:08 Vagrant Cascadian wrote:
> > > On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> > I use your original boot.scr
On Sat, 2014-06-14 at 15:37 -0700, Vagrant Cascadian wrote:
> On Sat, Jun 14, 2014 at 11:56:01PM +0200, Karsten Merker wrote:
> > On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> > It looks like you might not have set a console device, so
> > possibly the kernel boots, but you do no
On Sun, Jun 15, 2014 at 08:36:33AM +0200, Rainer Dorsch wrote:
> On Saturday 14 June 2014 14:48:08 Vagrant Cascadian wrote:
> > On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> I use your original boot.scr with an adapted bootargs:
...
> Variables set as you did, but the kernel is
On Sunday 15 June 2014 08:56:07 you wrote:
> On 15/06/2014 08:48, Rainer Dorsch wrote:
> > On Sunday 15 June 2014 08:43:23 you wrote:
> >> On 15/06/2014 08:36, Rainer Dorsch wrote:
> >>> Hi Ian,
> >>>
> >>> thanks for your useful response again.
> >>>
> >>> On Saturday 14 June 2014 14:48:08 Vagra
On Sunday 15 June 2014 08:43:23 you wrote:
> On 15/06/2014 08:36, Rainer Dorsch wrote:
> > Hi Ian,
> >
> > thanks for your useful response again.
> >
> > On Saturday 14 June 2014 14:48:08 Vagrant Cascadian wrote:
> >> On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> >>> root@bokoc
On Sunday 15 June 2014 08:46:30 Rainer Dorsch wrote:
> Hi Vagrant,
>
> On Saturday 14 June 2014 15:37:03 Vagrant Cascadian wrote:
> > On Sat, Jun 14, 2014 at 11:56:01PM +0200, Karsten Merker wrote:
> > > On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> > > It looks like you might n
On 15/06/2014 08:48, Rainer Dorsch wrote:
> On Sunday 15 June 2014 08:43:23 you wrote:
>> On 15/06/2014 08:36, Rainer Dorsch wrote:
>>> Hi Ian,
>>>
>>> thanks for your useful response again.
>>>
>>> On Saturday 14 June 2014 14:48:08 Vagrant Cascadian wrote:
On Sat, Jun 14, 2014 at 10:36:43PM +
On Sunday 15 June 2014 06:35:50 drEagle wrote:
> On 14/06/2014 22:36, Rainer Dorsch wrote:
> > Hi Ian,
> >
> > On Saturday 14 June 2014 14:23:33 you wrote:
> >> On Sat, 2014-06-14 at 14:42 +0200, Rainer Dorsch wrote:
> >>> On Saturday 14 June 2014 13:35:40 Ian Campbell wrote:
> Your boot comm
Hi Vagrant,
On Saturday 14 June 2014 15:37:03 Vagrant Cascadian wrote:
> On Sat, Jun 14, 2014 at 11:56:01PM +0200, Karsten Merker wrote:
> > On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> > It looks like you might not have set a console device, so
> > possibly the kernel boots, b
Hi Karsten,
thanks for your response.
On Saturday 14 June 2014 23:56:01 Karsten Merker wrote:
> On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> > I try to get the kernel up with manual tweaks in u-boot first:
> >
> > CPU: Freescale i.MX6Q rev1.2 at 792 MHz
> > Reset cause: POR
On 15/06/2014 08:36, Rainer Dorsch wrote:
> Hi Ian,
>
> thanks for your useful response again.
>
> On Saturday 14 June 2014 14:48:08 Vagrant Cascadian wrote:
>> On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
>>> root@bokocube:~# cat /root/boot.cmd
>>> 5# boot script for CuBox-i
>>
Hi Ian,
thanks for your useful response again.
On Saturday 14 June 2014 14:48:08 Vagrant Cascadian wrote:
> On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> > root@bokocube:~# cat /root/boot.cmd
> > 5# boot script for CuBox-i
> >
> > setenv device mmc
> > setenv partition ${mmcde
On 14/06/2014 22:36, Rainer Dorsch wrote:
> Hi Ian,
>
> On Saturday 14 June 2014 14:23:33 you wrote:
>> On Sat, 2014-06-14 at 14:42 +0200, Rainer Dorsch wrote:
>>> On Saturday 14 June 2014 13:35:40 Ian Campbell wrote:
Your boot command should load and then source the boot.scr which
flash
On Sat, Jun 14, 2014 at 11:56:01PM +0200, Karsten Merker wrote:
> On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> It looks like you might not have set a console device, so
> possibly the kernel boots, but you do not see any output. Try
> setting the console device on the kernel co
On Sat, Jun 14, 2014 at 10:36:43PM +0200, Rainer Dorsch wrote:
> root@bokocube:~# cat /root/boot.cmd
> 5# boot script for CuBox-i
>
> setenv device mmc
> setenv partition ${mmcdev}:${mmcpart}
> setenv bootargs 'quiet'
>
> image_locations='/boot/ /'
> kvers='3.15-rc8-armmp'
>
> for pathprefix in
On Saturday 14 June 2014 14:23:33 you wrote:
> On Sat, 2014-06-14 at 14:42 +0200, Rainer Dorsch wrote:
> > On Saturday 14 June 2014 13:35:40 Ian Campbell wrote:
> > > Your boot command should load and then source the boot.scr which
> > > flash-kernel has created, it contains the right things and is
On Saturday 14 June 2014 14:23:33 you wrote:
> On Sat, 2014-06-14 at 14:42 +0200, Rainer Dorsch wrote:
> > On Saturday 14 June 2014 13:35:40 Ian Campbell wrote:
> > > Your boot command should load and then source the boot.scr which
> > > flash-kernel has created, it contains the right things and is
Hi Ian,
On Saturday 14 June 2014 14:23:33 you wrote:
> On Sat, 2014-06-14 at 14:42 +0200, Rainer Dorsch wrote:
> > On Saturday 14 June 2014 13:35:40 Ian Campbell wrote:
> > > Your boot command should load and then source the boot.scr which
> > > flash-kernel has created, it contains the right thin
On Sat, 2014-06-14 at 14:46 +0200, Rainer Dorsch wrote:
> I still have issues to boot a cubox-i with the u-boot supplied by
> Debian, but maybe I install it the wrong way.
I'm afraid I don't know anything about the specifics of the cubox. But:
> E.g. I do not see the environment overwritten to de
On Sat, 2014-06-14 at 14:42 +0200, Rainer Dorsch wrote:
> On Saturday 14 June 2014 13:35:40 Ian Campbell wrote:
> > Your boot command should load and then source the boot.scr which
> > flash-kernel has created, it contains the right things and is
> > automatically updated when the kernel/initramfs/
Hi Ian,
> I don't have a cubox but I was under the impression that the default
> u-boot environment (at least for the u-boot packaged in Debian) would Do
> The Right Thing.
I still have issues to boot a cubox-i with the u-boot supplied by Debian, but
maybe I
install it the wrong way.
u-boot c
Hi Ian,
On Saturday 14 June 2014 13:35:40 Ian Campbell wrote:
> On Sat, 2014-06-14 at 14:18 +0200, Rainer Dorsch wrote:
> > The only thing I am wondering is why does it not create a symlink into the
> > root directory, as there is one for vmlinuz and initrd:
> >
> > root@bokocube:/# ln -s /boot/d
On Sat, 2014-06-14 at 14:18 +0200, Rainer Dorsch wrote:
> The only thing I am wondering is why does it not create a symlink into the
> root directory, as there is one for vmlinuz and initrd:
>
> root@bokocube:/# ln -s /boot/dtb-3.15-rc8-armmp dtb-armmp
>
> ?
Those symlinks are created by the ke
Hello,
I just saw that flash-kernel works now on the cubox-i4pro:
Setting up linux-image-3.15-rc8-armmp (3.15~rc8-1~exp1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-3.15-rc8-armmp
Installing imx6q-cubox-i.dtb 3.15-rc8-armmp into /boot
Installing imx6
44 matches
Mail list logo
