On Sun, 2016-07-31 at 13:16 -0700, Martin Michlmayr wrote:
> Package: flash-kernel
> Version: 3.68
>
> At the moment, flash-kernel doesn't exit when the DTB doesn't exist.
> It will print the DTB to be used but then not copy it. That will
> result in devices not being able to boot.
>
> Ian, is t
Adam D. Barratt (2016-07-30):
> On Wed, 2016-07-27 at 15:07 +0200, Andrew Shadura wrote:
> > On 21/07/16 12:19, Adam D. Barratt wrote:
> > >
> > > On 2016-07-21 11:01, Adam D. Barratt wrote:
> > >> Control: tags -1 -moreinfo +confirmed
> > > [...]
> > >> +wpa (2.3-1+deb8u4) jessie-security; urgen
Package: flash-kernel
Version: 3.68
At the moment, flash-kernel doesn't exit when the DTB doesn't exist.
It will print the DTB to be used but then not copy it. That will
result in devices not being able to boot.
Ian, is there a reason why we *don't* want to exit?
Right now we have:
get_dtb_nam
* Ian Campbell [2016-07-31 10:20]:
> I've attached the two patches I had sitting in my branch here, they
> look sensible but I honestly can't remember what state they are in.
>
> AFAICT the main difference is that they preserve the directory layout
> rather than collapsing it. Not sure there is a
Hi Martin,
Sure. It may take me a few days to get some time, but I'll give it a try
and let you know how it goes.
Mike
On Sat, Jul 30, 2016 at 7:23 PM, Martin Michlmayr wrote:
> Mike, can you please give these instructions a go? This is what I
> intend to post to the mv2120 list.
>
> --
>
>
* Ian Campbell [2016-07-31 10:14]:
> > Are all arm64 boards only going to support booti and not bootz?
>
> bootz refers to the zImage which is only an ARM image type and not an
> ARM64 one, which is an Image and hence booti.
And according to this email, all arm64 boards will have booti soon:
htt
* Jeffrey Walton [2016-07-31 11:42]:
> Primarily because its a port: https://www.debian.org/ports/ and
> https://www.debian.org/ports/arm/ .
>
> Other, lesser reasons include there's no documentation (follow the
> links above), and using non-port procedures fails sooner than the
> ports procedure
Your message dated Sun, 31 Jul 2016 17:14:14 +0100
with message-id <20160731161414.gx13...@einval.com>
and subject line Re: Bug#833072: Can't create armel chroot using debootstrap -
Invalid Release file, no entry for main/binary-armel/Packages
has caused the Debian Bug report #833072,
regarding Ca
>>Results from host computer:
>>
>>I: Running command: debootstrap --arch armel --foreign --keyring
>>/usr/share/keyrings/debian-ports-archive-keyring.gpg --variant=buildd
>>--exclude=debfoster unstable debian-armel
>>http://ftp.ports.debian.org/debian-ports
>>I: Retrieving Release
>>I: Retrieving
On Sun, Jul 31, 2016 at 09:42:23AM -0400, Jeffrey Walton wrote:
>Package: debootstrap
>Version: 1.0.81
>Severity: important
>
>The host computer is running Debian Sid, fully patched.
>
>Results from host computer:
>
>I: Running command: debootstrap --arch armel --foreign --keyring
>/usr/share/keyri
Package: debootstrap
Version: 1.0.81
Severity: important
The host computer is running Debian Sid, fully patched.
Results from host computer:
I: Running command: debootstrap --arch armel --foreign --keyring
/usr/share/keyrings/debian-ports-archive-keyring.gpg --variant=buildd
--exclude=debfoster
Control: tag -1 patch
stop
On Sun, Jul 31, 2016 at 07:02:03PM +0900, Jonny wrote:
> --- /a/setupcon
> +++ /b/setupcon
> @@ -911,7 +911,7 @@
> if ls /dev/fb* >/dev/null 2>/dev/null; then
> for i in /dev/vcs[0-9]*; do
> {
> -$commands_f
> +${commands_f:-:}
>
Processing control commands:
> tag -1 patch
Bug #833053 [console-setup] Syntax error in the script that setupcon outputs
Added tag(s) patch.
--
833053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: console-setup
Version: 1.148
Hi,
if you choose "Do not change the boot/kernel font" in debconf questions '"VGA"
has a traditional appearance and has medium coverage of ...', and outputs the
"/etc/console-setup/cached_setup_font.sh" such as the following.
#!/bin/sh
if ls /dev/fb* >/
On Sat, 2016-07-30 at 16:52 -0700, Martin Michlmayr wrote:
> DTBs on arm64 are stored as vendor/dtb rather than everything in one
> directory.
I looked at this a while back but it seems I never completed it, or at
least never pushed it :-(.
I've attached the two patches I had sitting in my branch
On Sat, 2016-07-30 at 17:14 -0700, Vagrant Cascadian wrote:
>
> Are all arm64 boards only going to support booti and not bootz?
bootz refers to the zImage which is only an ARM image type and not an
ARM64 one, which is an Image and hence booti.
That would only change if someone added a self-decom
16 matches
Mail list logo
