2012-04-25 12:52:15.0
-0700
+++ debian/changelog2012-04-25 13:13:40.0 -0700
@@ -1,3 +1,10 @@
+linux-2.6 (3.2.15-2) UNRELEASED; urgency=low
+
+ [ Vagrant Cascadian ]
+ * [armhf/vexpress] New kernel variant to support Versatile Express.
+
+ -- Vagrant Cascadian Wed, 25 Ap
On Tue, Dec 17, 2013 at 09:58:17AM +, Ian Campbell wrote:
> On Tue, 2013-12-17 at 13:31 +0800, Niew, Sh. wrote:
> > On Dec 13, 2013, at 6:34 PM, Ian Campbell wrote:
> > > On Fri, 2013-12-06 at 13:54 +0800, Niew, Sh. wrote:
> > > [...]
> > >> Is it ahci_imx need ahci_platform compile with yes?
On Thu, Dec 26, 2013 at 01:14:49PM +, David Pottage wrote:
> On 25/12/13 17:37, Luke Kenneth Casson Leighton wrote:
> >just something for people's attention, this is a pretty damn good find
> >by erix: quad-core 1ghz iMX6, it has 2gb of RAM, SATA, GbE and a full
> >MiniPCIe slot (not just USB-o
On Sun, Apr 20, 2014 at 04:28:45PM +0100, Ian Campbell wrote:
> On Sun, 2014-04-20 at 16:13 +0100, Ben Hutchings wrote:
> > Given that, it seems like a good time to add arm64 to src:linux with a
> > configuration that will run on at least a typical QEMU ARM64 emulation.
>
> AIUI qemu 2.0 only does
On Mon, Apr 28, 2014 at 11:01:06PM +0200, Karsten Merker wrote:
> On Sun, Apr 27, 2014 at 07:35:35AM +0100, Ian Campbell wrote:
>
> > I think u-boot has some sh-style control loops you can use? (for x in
> > fstype1 fstype2; do ...). People keep saying one can just use "fsload"
> > too, but I've n
On Mon, Apr 21, 2014 at 09:34:04PM -0400, James Valleroy wrote:
> The 2nd version of this script [2] uses the kernel and dtbs from
> debian's linux-image-armmp package. But I can't get farther than
> "Starting kernel ..." (log is at [3]).
I just submitted a patch to the BTS to enable some options
On Fri, May 16, 2014 at 07:39:09PM +0100, RichardBown wrote:
> and trying to run
> sudo debootstrap --arch armel wheezey work/ http://ftp.us.debian.org/debian
>
> E: No such script: /usr/share/debootstrap/scripts/wheezey
Try "wheezy" instead. :P
live well,
vagrant
signature.asc
Description
On Fri, May 16, 2014 at 10:45:19PM +0100, peter green wrote:
> To do the second stage you have two options. Either you can do the second
> stage with user mode qemu or you can do it on the device. To do it with qemu
> you would do.
>
> apt-get install qemu-arm-static binfmt-support
> cp /usr/bin/q
On Sun, May 18, 2014 at 07:41:58PM +0200, Karsten Merker wrote:
> attached is a small patch against flash-kernel to add machine db
> entries for the Cubieboard 1/2 and the Mele A1000.
...
> I'll probably get access to a Cubieboard2 sometime next week and
> will test an installation on it, but for
On Fri, May 30, 2014 at 05:33:14PM +0200, Rainer Dorsch wrote:
> I did not have Debian's u-boot. I tested it now, but does not work at all
> for me.
>
>
> I dd ed SPL and u-boot.img from /usr/lib/u-boot/mx6_cubox-i/.
>
> But that did not change anything for bootz, still it does not detect the
>
On Fri, May 30, 2014 at 07:13:49PM +0200, Rainer Dorsch wrote:
> On Friday 30 May 2014 09:53:09 Vagrant Cascadian wrote:
> > On Fri, May 30, 2014 at 05:33:14PM +0200, Rainer Dorsch wrote:
...
> > bootcmd=run loadkernel ; run loadinitrd ; run loadfdt ; bootz ${loadaddr}
&g
On Fri, May 30, 2014 at 07:59:29PM +0100, Ian Campbell wrote:
> On Fri, 2014-05-30 at 17:27 +0200, Steve Langasek wrote:
> > diff --git a/db/all.db b/db/all.db
> > index 68f85b4..dce775d 100644
> > --- a/db/all.db
> > +++ b/db/all.db
> > @@ -436,6 +436,23 @@ Boot-DTB-Path: /boot/dtb
> > Required-P
On Fri, May 30, 2014 at 12:36:03PM +0200, Rainer Dorsch wrote:
> 3) The functionality is limited, e.g. no video out, only serial console
>
> Not a serious issue for me, because that is enough is running for my usecase
> right now. But I wanted to mention that in case others follow that way and
> o
On Fri, May 30, 2014 at 11:40:09PM +0200, Rainer Dorsch wrote:
> On Friday 30 May 2014 12:44:59 Vagrant Cascadian wrote:
> Is also support for wireless included?
>
> According to http://wiki.gentoo.org/wiki/Cubox-i#Wifi
>
> CONFIG_BRCMUTIL=y
> CONFIG_BRCMFMAC=y
>
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 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 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,
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...
>
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_pr
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 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:
> > >
On Sat, Jun 28, 2014 at 07:22:36PM +0200, Rainer Dorsch wrote:
> you updated https://wiki.debian.org/ArmHardFloatPort/CuBox-i with
>
> "The 3.15.1-1~exp1+ kernel in experimental also includes support for
> framebuffer video over HDMI."
...
> and get console output on HDMI. It is not entirely ali
On Wed, Jul 02, 2014 at 10:24:31AM +0800, Paul Wise wrote:
> Platform firmware is an odd beast in the world of software.
Thanks for raising this challenging topic!
> On ARM the platform firmware is way less standardised but is often
> u-boot. u-boot mainline is packaged and apparently has suppo
On Sun, Jul 06, 2014 at 02:20:03PM +0200, Rainer Dorsch wrote:
> I have reinstalled my cubox-i and I revised my notes and want to share them
>
> http://bokomoko.de/~rd/Debian/cubox-i-notes.txt
>
> since they have been useful for me during reinstallation.
Thanks for sharing your thorough notes!
I've been working on updating to the soon-to-be-released u-boot v2014.07,
but the armel builds fail with the openrd_ultimate and sheevaplug targets.
Without the debian-specific patches, it builds fine, but also may lack sata,
mmc and/or other features that have been present in Debian's u-boot pack
On Thu, Jul 10, 2014 at 11:30:20AM +0800, Paul Wise wrote:
> On Wed, Jul 9, 2014 at 1:53 PM, Vagrant Cascadian wrote:
>
> > the debian-specific patches
>
> Would it be possible to get these merged upstream so we don't have
> this issue in future?
I new I left som
On Thu, Jul 10, 2014 at 09:04:49AM +0200, drEagle wrote:
> My patch was taken by Debian (thanks for this) the only MMC enabled uboot for
> SheevaPlugs.
>
> Mainline u-boot had (again) change the initialization process for MMC [1] so
> I had made some quick revisions of the MVSDIO driver.
>
> >>
On Fri, Jul 11, 2014 at 05:47:18AM +0200, drEagle wrote:
> On 10/07/2014 21:30, Vagrant Cascadian wrote:
> > On Thu, Jul 10, 2014 at 09:04:49AM +0200, drEagle wrote:
> > openrd_ultimate still fails to build:
>
> You need to add #define CONFIG_GENERIC_MMC inside the MMC block
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 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 o
On Sun, Jul 13, 2014 at 02:15:16PM +0100, Neil Williams wrote:
> On Sun, 13 Jul 2014 11:48:54 +0100
> Neil Williams wrote:
>
> > On Sun, 13 Jul 2014 10:32:46 +0100
> > Ian Campbell wrote:
> > > Why ISOs BTW? They don't seem all that typical on ARM systems,
> >
> > As a route to the default pack
On Sun, Jul 13, 2014 at 01:39:09PM +0200, Rainer Dorsch wrote:
> At the end, it turned out that Debian u-boot does not work for the cubox-
> i2ultra. The u-boot SPL is not started on the cubox-i2ultra (i.e. no outputs
> on the serial console, no red front light).
Thanks for testing! Sorry to hear
On Sun, Jul 13, 2014 at 10:38:18AM -0700, Steve Langasek wrote:
> On Sun, Jul 13, 2014 at 09:37:39AM -0700, Vagrant Cascadian wrote:
> > But yes, 2014.07-rc4 appears to include support for SPL on imx6, although
> > the only board using it is gw_ventana. It might be feasible to
On Mon, Jul 14, 2014 at 08:57:15AM +0100, Neil Williams wrote:
> On Sun, 13 Jul 2014 09:29:39 -0700
> Vagrant Cascadian wrote:
>
> > On Sun, Jul 13, 2014 at 02:15:16PM +0100, Neil Williams wrote:
> > > On Sun, 13 Jul 2014 11:48:54 +0100
> > > Neil Williams w
On Tue, Jul 15, 2014 at 07:03:44PM +0100, Neil Williams wrote:
> On Tue, 15 Jul 2014 13:22:04 +0100 Ian Campbell wrote:
>
> > On Sun, 2014-07-13 at 11:48 +0100, Neil Williams wrote:
> > Is there even any ARM platform out there with a optical drive on it?
>
> ISOs are not just about optical driv
On Sun, Jul 20, 2014 at 12:54:06PM +0100, Neil Williams wrote:
> On Sun, 13 Jul 2014 09:29:39 -0700 Vagrant Cascadian
> wrote:
> > I've been enabling things like bootz and ext4 support in recently
> > added boards in Debian's u-boot, I can look into enabling for th
On 2014-08-03, Rainer Dorsch wrote:
>> Debian jessie could likely go final around December and
>> predictions are the jessie kernel will be 3.16. My hope is full support for
>> the Cubox hardware is mainlined into the 3.16 by then - a year after I
>> purchased the device.
>
> I am not a kernel ex
On 2014-08-20, Robert Nelson wrote:
> On Wed, Aug 20, 2014 at 3:21 PM, Andrew M.A. Cater
> wrote:
>> I've a Beaglebone Black running Debian 7.6 with some wheezy-backports
>> packages. This is installed on both the internal eMMC flash and also
>> 7.6 installed on the SD card.
>>
>> What's the best
On 2014-08-06 22:39:38 -0700, Gérald Kerma wrote:
> On 07/08/2014 07:19, Paul Wise wrote:
>> On Thu, 2014-08-07 at 06:11 +0200, Gérald Kerma wrote:
>>> Thank's to Debian team who add support of all versions of MVSDIO driver in
>>> the debian u-boot package.
>>
>> Will these be merged too?
>
> Th
I'm looking for people willing to test u-boot targets on an ongoing
basis for various platforms. While I have a handful of boards I can test
on, I don't have the hardware or perhaps more importantly, the time to
always test on all of them.
I hope this sounds like a reasonable approach to folks...
On 2014-09-07 13:48:30 -0500, Karsten Merker wrote:
> Vagrant, if possible it would be nice if you could enable the
> following targets in your next build of u-boot 2014.10 for armhf:
>
> A10-OLinuXino-Lime
> A10s-OLinuXino-M
> A13-OLinuXino
> A13-OLinuXinoM
> A20-OLinuXino_MICRO
> Cubieboard2
> Cu
On 2014-09-07 13:48:30 -0500, Karsten Merker wrote:
> Vagrant, if possible it would be nice if you could enable the
> following targets in your next build of u-boot 2014.10 for armhf:
>
> A10-OLinuXino-Lime
> A10s-OLinuXino-M
> A13-OLinuXino
> A13-OLinuXinoM
> A20-OLinuXino_MICRO
> Cubieboard2
> Cu
On 2014-09-08 04:26:48 -0500, Ian Campbell wrote:
> Ideally we would build FEL variants for all sunxi boards, but we don't
> have _FEL defconfigs for everything upstream. Hans (my co-custodian)
> rightly doesn't want to duplicate every defconfig twice.
>
> At the weekend I was playing with the two
On 2014-09-08 11:54:01 -0500, Ian Campbell wrote:
> On Mon, 2014-09-08 at 11:31 -0500, Vagrant Cascadian wrote:
>> I'm wondering if u-boot shouldn't just take advantage of executable
>> debhelper files or arch-specific debhelper files and simplify
>> debian/rules con
On 2014-09-21 17:17:23 -0500, Karsten Merker wrote:
> I believe that on armhf systems a tarball makes more sense than
> a disk image for the following reasons:
Thanks for working on this!
> - We do not install a boot sector on armhf but just a u-boot
> script. This is a normal file which can
On 2014-09-17 07:13:45 -0500, Christian Kastner wrote:
> On 2014-09-13 10:53, Karsten Merker wrote:
>> Vagrant, as Christian has comitted to provide testing on the
>> A20-OLinuXino-LIME, could you enable that target as well with
>> the next upstream release?
Should hit experimental shortly, along
On 2014-09-30 15:47:13 -0700, Karsten Merker wrote:
> * Add the "console=" parameter to bootargs only if ${console}
> is set.
...
> diff --git a/build/boot/arm/bootscr.mainline_common
> b/build/boot/arm/bootscr.mainline_common
...
> +if test -z "${console}"; then
> + setenv bootargs "${boot
On 2014-10-03, peter green wrote:
> I started looking for ways to make the boot script detect whether it was
> running on the boundary u-boot or the debian u-boot. There is apparently
> a u-boot variable called "ver" but unfortunately neither the debian or
> the boundary u-boot had it turned on.
On 2014-10-19, Paul Wise wrote:
> On Mon, Oct 20, 2014 at 1:09 AM, Steve McIntyre wrote:
>> On Sun, Oct 19, 2014 at 10:27:30AM -0400, Martin Michlmayr wrote:
>>>* Paul Wise [2014-10-18 15:58]:
Debian's "hardware wanted" web page says that the ARM porters (Riku
Voipio and Martin Michlmayr
On 2014-10-01, Karsten Merker wrote:
> On Wed, Oct 01, 2014 at 07:01:44AM +0200, Cyril Brulebois wrote:
>> Karsten Merker (2014-10-01):
> attached is V3 of the patch. I have run a full armhf installer
> build with it without problems and I have done two test installs
> on a Cubietruck with the re
On 2014-11-10, Karsten Merker wrote:
> On Mon, Nov 10, 2014 at 11:52:54PM +0100, Rainer Dorsch wrote:
>> I am wondering if there is a debian installer image for armhf for cubox-
>> i/armhf.
>>
>> If yes, any documentation on how the installer process works (e.g. boots
>> from
>> USB, installs on
On 2014-11-15, Rainer Dorsch wrote:
> On Saturday 15 November 2014 11:51:05 Karsten Merker wrote:
> What is the difference between u-boot-spl.bin and SPL in
...
> -rw-r--r-- 1 root root 31744 Nov 2 01:32 SPL
> -rw-r--r-- 1 root root 302872 Nov 2 01:32 uboot.elf
> -rw-r--r-- 1 root root 236248
Package: partman-base
Version: 179
Severity: important
Tags: patch
Several armhf platforms have u-boot installed directly to the device
in an area which gets wiped out by partman. This results in
debian-installer producing a "successful" install, but zeros out the
location of the bootloader in the
On 2014-12-03, Karsten Merker wrote:
> several armhf systems do not have u-boot (or another firmware) in
> non-volatile (i.e. ROM/Flash) memory, but instead store their
> system firmware on a removable medium such as an SD card.
...
> Debian provides appropriate u-boot images for several supported
On 2014-12-06, Karsten Merker wrote:
> On Wed, Dec 03, 2014 at 03:10:37PM -0800, Vagrant Cascadian wrote:
>
> [providing u-boot images for armhf platforms that do not have
> u-boot in non-volatile storage]
...
> I guess it would make sense to provide both the "naked" u-b
On 2014-12-18, Karsten Merker wrote:
> just to avoid double work: I have recently started working on implementing
> image building support (both for "bare" u-boot images as well as for "full"
> images with u-boot + kernel + initrd) and I hope to find some time over
> Christmas to finish a working p
On 2014-12-23, Karsten Merker wrote:
> Attached is a set of patches to implement building bootable
> d-i images for armhf systems. It offers various options:
>
> - provide binary "u-boot-only" images for people who want to
> manually install u-boot and e.g. run the rest of the setup via
> tftp
On 2014-12-26, Karsten Merker wrote:
> On Tue, Dec 23, 2014 at 02:17:16PM -0800, Vagrant Cascadian wrote:
>> On 2014-12-23, Karsten Merker wrote:
>> I don't think it's possible yet to have the device-independent parts
>> working with *all* platforms (at least fo
On 2014-12-28, Karsten Merker wrote:
> If they do,
> we will also need to enable building u-boot for the pcduino3
> (CCing Vagrant Cascadian, the u-boot maintainer).
>
> @Vagrant: the board is supported in u-boot v2014-10
> (Linksprite_pcDuino3_defconfig).
Happy to enable it in
On 2014-12-28, Ian Campbell wrote:
> OOI, do you know how broken the white is when booting with the black's
> DTB? Completely unusable, missing some minor peripheral or somewhere in
> the middle?
They are very similar, but I'm not familiar enough with the white to
know for sure.
Maybe someone on
On 2014-12-28, Robert Nelson wrote:
> On Sun, Dec 28, 2014 at 6:26 PM, Vagrant Cascadian wrote:
>> On 2014-12-28, Ian Campbell wrote:
>>> OOI, do you know how broken the white is when booting with the black's
>>> DTB? Completely unusable, missing some minor pe
On 2014-12-29, Ian Campbell wrote:
> Given the beaglebone specific findfdt which Robert links to above
Several other ti platforms also use findfdt, FWIW.
> could we add a check to bootscr.beaglebone which refuses to boot on a
> white? (looks like we can look at $board_name directly).
Yes, that
On 2014-12-29, Ian Campbell wrote:
> On Mon, 2014-12-29 at 08:48 -0800, Vagrant Cascadian wrote:
>> On 2014-12-29, Ian Campbell wrote:
>> > could we add a check to bootscr.beaglebone which refuses to boot on a
>> > white? (looks like we can look at $board_name directl
On 2014-12-30, Ian Campbell wrote:
> I should start by saying that I'm not personally particularly interested
> in this functionality, but I don't want to be a blocker for people who
> are so since I've been asked I'll give my 2pence...
Thanks for taking the time.
> I've been wondering if this i
On 2015-01-01, Karsten Merker wrote:
> +++ b/build/boot/README.concatenateable_images
...
> +To create a complete image from the two parts on Linux systems, you can
> +use zcat (for .gz images), bzcat (for .bz2 images) or xzcat (for .xz
> +images) as follows:
> +
> + zcat firmware..img.gz partitio
On 2015-01-02, Ian Campbell wrote:
> On Tue, 2014-12-30 at 13:42 -0800, Vagrant Cascadian wrote:
>> On 2014-12-30, Ian Campbell wrote:
>> I think the difference is one is a set of netboot images, and the other
>> is a set of hd-media images.
>
> But what is the d
On 2015-01-07, Ian Campbell wrote:
> On Fri, 2015-01-02 at 08:59 -0800, Vagrant Cascadian wrote:
>> On 2015-01-02, Ian Campbell wrote:
>> > On Tue, 2014-12-30 at 13:42 -0800, Vagrant Cascadian wrote:
>> >> On 2014-12-30, Ian Campbell wrote:
> But I still have a qu
On 2015-01-05, Cyril Brulebois wrote:
> Karsten Merker (2015-01-02):
>> Ok, I'll change the wording for V4. My intention was to provide a
>> generic README that works regardless of which compression options
>> one chooses in the makefile, so that switching from .gz to .xz
>> would be simple withou
Package: src:linux
Version: 3.16.7-ckt4-3
Severity: wishlist
Tags: patch
Please consider enabling CONFIG_BACKLIGHT_GPIO as a module in the
armmp kernel.
This module enables support for the BeagleBone Black with the LCD7
cape (although still requires a custom .dtb). It may also be useful to
other
On 2015-03-13, Stuart Winter wrote:
> Trying to reboot on my Banana Pi using this kernel doesn't work -the OS
> shuts down but the Banana Pi never reboots.
> I had a look at the Fedora Kernel (Linux 4.x) which has the same problem.
>
> http://ftp.de.debian.org/debian/pool/main/l/linux/kernel-image-
It seems that OpenRD Ultimate with u-boot 2015.04-rc3 and newer no
longer builds from source, both in Debian and with mainline git. It
appears to have overgrown the size limits set for it:
OBJCOPY u-boot.srec
OBJCOPY u-boot.bin
u-boot.bin exceeds file size limit:
limit: 393216 bytes
actua
On 2015-03-28, Gerald Kerma wrote:
> Signed-off-by: Gerald Kerma
> ---
> debian/patches/guruplug_mvfs_and_mmc.diff | 10 --
> 1 file changed, 10 deletions(-)
Thanks for the patches!
It would be best to submit these as bugs against u-boot, rather than the
debian-arm list.
What u-boot ve
On 2015-03-25, drEagle wrote:
> Le 21/03/2015 15:53, Vagrant Cascadian a écrit :
>> It seems that OpenRD Ultimate with u-boot 2015.04-rc3 and newer no
>> longer builds from source, both in Debian and with mainline git. It
>> appears to have overgrown the size limits set for i
On 2015-03-31, Arne Ploese wrote:
> So I got this to work...
>
> 1. Build u-boot for micro:
> Get the sources:
> $apt-get --compile --host-architecture=armhf source u-boot-sunxi
> after build failed
> $cd u-boot-2014.10+dfsg1
> $make CROSS_COMPILE=arm-linux-gnueabihf- A20-OLinuXino_MICRO_defconfig
On 2015-03-29, drEagle wrote:
> Already done for guruplug so the actual debian patch can be removed.
>
>> What u-boot versions should they be applied to?
>
> upstream aster since 201501.
Thanks for getting patches upstream!
Ok, I've removed the patch in the experimental-2014.04 branch in
Debian's
On 2015-04-20, Neil Williams wrote:
> On Mon, 20 Apr 2015 09:21:52 -0500
> Robert Nelson wrote:
>
>> On Mon, Apr 20, 2015 at 9:10 AM, Robert Nelson
>> wrote:
>> > On Mon, Apr 20, 2015 at 7:49 AM, Neil Williams
>> > wrote:
>> >> These instructions: https://wiki.debian.org/PandaBoard don't give a
On 2015-04-29, Rick Thomas wrote:
> Now that I’ve got my cubox-i4pro running from the micro-SD card, I’d
> like to try getting it to run from my eSATA disk (which is *much*
> faster than the uSD card!)
>
> I assume there is some u-boot magic needed to make this work? Anything else?
You need to st
On 2015-04-27, Nigel Sollars wrote:
> I was wondering if someone could give the steps of installing Jessie from a
> netinstall to a micro sd card ( say for a BeagleBone Black ) .. then when
> the install is complete, what would be the requirements to push that to
> the emmc flash?.
Unfortunately,
On 2015-04-29, Rick Thomas wrote:
> On Apr 29, 2015, at 1:29 PM, Vagrant Cascadian wrote:
>> On 2015-04-29, Rick Thomas wrote:
>>> Now that I’ve got my cubox-i4pro running from the micro-SD card, I’d
>>> like to try getting it to run from my eSATA disk (which is *much*
&
On 2015-04-20, Robert Nelson wrote:
> On Mon, Apr 20, 2015 at 7:49 AM, Neil Williams wrote:
>> These instructions: https://wiki.debian.org/PandaBoard don't give a
>> bootable SD card for the panda-es:
>>
>> U-Boot SPL 2014.10+dfsg1-5 (Apr 07 2015 - 22:19:50)
>> OMAP4460 ES1.1
>> SPL: Please implem
r, I
>> noticed that even the Ultimate target was removed in Debian's u-boot
>> recently:
>> http://anonscm.debian.org/cgit/collab-maint/u-boot.git/commit/debian/targets?id=ea2f6ce84b7788cda2cb7deb29690cb368451e8c
>>
>> So if you want to work out why it doesn'
On 2015-06-21, Karsten Merker wrote:
> If we don't pass a console variable to the kernel, d-i starts
> on the console device defined by the platform's stdout-path
> property, i.e. usually on a serial console - again bad luck
> for people having only a framebuffer console.
>
> If we set the console
On 2015-07-19, Paul van der Vlis wrote:
> I have a Lime2 and it works with the Olimex Debian image, but I want to
> use the Debian installer.
>
> I've downloaded the lime2 firmware and partition.img.gz and put this on
> a SD-card following the wiki [1].
>
> I don't see a DHCP request on the server
On 2015-08-25, Rick Thomas wrote:
> On Aug 25, 2015, at 12:53 AM, Tim Fletcher wrote:
>>> On 25 Aug 2015, at 01:39, Rick Thomas wrote:
>>> What is in the default environment?
>>> It boots just fine, so the default environment must be up to the job, but
>>> I’m curious.
>> It's part of the u-boot
On 2014-09-30, Ben Hutchings wrote:
> On Tue, 2014-09-30 at 08:19 +0100, Ian Campbell wrote:
>> On Fri, 2014-09-26 at 00:08 +0100, Ben Hutchings wrote:
>> > However, at the moment initramfs-tools won't include PHY drivers even in
>> > that configuration.
>>
>> I spent some time last week hunting f
On 2015-11-19, Pierre wrote:
> I've bootstrapped Jessie on my Cubox-i 4 following instructions from
> http://techieventures.blogspot.ca/2014/10/install-debian-jessie-with-debian-u.html.
I'd recommend trying the images for debian-installer instead, as those
*should* set up booting correctly:
ht
On 2015-11-21, Pierre wrote:
> On Thursday 19 November 2015 21:13:34 Vagrant Cascadian wrote:
>> But in general, I'd recommend against using uEnv.txt, as it's not
>> supported in mainline u-boot for the Cubox-i, and not supported in newer
>> versions of u-boot i
On 2015-11-23, Pierre wrote:
> Objective: Install Debian Jessie on a USB hard drive for a Cubox-i 4Pro
>
> Steps:
> 1. On a linux host, create a bootable SD card with Debian installer image from
> http://ftp.us.debian.org/debian/dists/jessie/main/installer-armhf/current/images/netboot/SD-card-image
On 2015-12-01, Ian Campbell wrote:
> On Tue, 2015-12-01 at 16:10 +, Mark Morgan Lloyd wrote:
>> > With respect to mainline kernel support, this page shows a pretty good
>> > picture:
>> > http://elinux.org/RPi_Upstreaming
>> >
>> > Many of the drivers are already upstreamed or queued for 4.4
On 2015-12-09, Mark Morgan Lloyd wrote:
> A quirk of the RPi appears to be with with the standard loader (i.e.
> rather than going via something like U-Boot) it doesn't use an initrd.
> This appears to be causing people problems if they want to do something
> like moving their main filesystem on
Anyone able to commit to testing new u-boot versions with a riotboard:
https://wiki.debian.org/U-boot
If you have a riotboard, and wouldn't mind committing to testing new
versions and being called on to troubleshoot issues, please respond to
the bug report:
https://bugs.debian.org/807850
l
I'm trying to get a Cubieboard4 board booting.
It looks like the Cubieboard4 has support in mainline linux since at
least 4.2 (so should work with jessie-backports), but I can't find a
u-boot that will boot it...
I see that Karsten added a flash-kernel entry for it, but it isn't
supported in main
On 2016-01-05, Rick Thomas wrote:
> When running Debian (Sid, in this case) and I do “fw_printenv” it
> gives an error message about a bad CRC and using default environment…
>
>> rbthomas@sheeva:~$ sudo fw_printenv
>> Warning: Bad CRC, using default environment
>> bootargs=
>> bootcmd=
...
> This i
On 2016-01-05, Rick Thomas wrote:
> On Jan 5, 2016, at 11:16 AM, Rick Thomas wrote:
>> The only thing I see that looks like a warning is a mention of it not
>> using “generic board”.
>
> It turns out that this may, in fact, be relevant. Googling for
> “README.generic-board” gives
>
> https://
On 2016-01-05, Rick Thomas wrote:
> On Jan 5, 2016, at 12:17 PM, Vagrant Cascadian wrote:
>> Well, I would like to know if the newer versions in Debian are or aren't
>> working, if you'd be willing to try. They do still build in 2016.01~rc3,
>> so newer versions
On 2016-01-06, Rick Thomas wrote:
> I’ll try your 2016.01~rc3+dfsg1-3 from experimental as soon as I can.
Great, thanks.
> Just to be sure of what I need to do:
>
> 1) Install the new versions of Debian packages for u-boot and u-boot-tools on
> my test SheevaPlug Debian (currently running Sid)
On 2016-01-06, Rick Thomas wrote:
> For what it’s worth, by grepping about in /dev/mtd0, I located what
> seems to be the place where the u-boot environment is located.
>
> It’s 0x8.
>
> And to verify that, I have changed /etc/fw_env.config to
>
>> # MTD device name Device offset Env. size
On 2016-01-11, Albert ARIBAUD wrote:
> On Sun, 10 Jan 2016 21:39:13 +0100, Philip Hands wrote:
>> Martin Michlmayr writes:
>> > * Albert ARIBAUD [2016-01-01 13:58]:
...
>> > I see that you've re-introduced OpenRD support upstream, including
>> > support for OpenRD-Base and OpenRD-Client.
>
> Ye
On 2015-12-29, Ian Campbell wrote:
> On Tue, 2015-12-29 at 12:15 +0100, Karsten Merker wrote:
>> On Mon, Dec 28, 2015 at 02:45:33PM -0800, Vagrant Cascadian wrote:
>> > I'm trying to get a Cubieboard4 board booting.
>> >
>> > It looks like the Cubieboard4
On 2016-02-11, toogley wrote:
> i have a Banana Pro which i want to boot a debian jessie from. I know
> HDMI doesn't work, so I want to have a serial connection for configuring
> ssh.
...
> 4. My Banana Pro has three pins in the corner of the LAN Port. I've
> connected my
> Pins accoring tha
1 - 100 of 249 matches
Mail list logo
