Re: Updating kernel for Debian Jessie on iMX53 QuickStart

2016-01-12 Thread Mike Thompson
To make the flash-kernel package produce the correct files that match a Jessie installation created by the following instructions: https://wiki.debian.org/InstallingDebianOn/Freescale/QuickStart I had to update Freescale i.MX53 records in the '/usr/share/flash-kernel/db/all.db' file with the foll

Re: Updating kernel for Debian Jessie on iMX53 QuickStart

2016-01-12 Thread Mike Thompson
I didn't know about the flash-kernel package nor had it installed. I installed the package, but it unfortunately produces a uImage and/or uInitrd files that fail to boot. I'll have to debug the script to understand why it's not working. However, thanks for the tip that got me part of the way the

Re: I/O issues with writing to mtdblock devices on kirkwood

2016-01-12 Thread Arnd Bergmann
On Tuesday 12 January 2016 22:00:58 Mark Brown wrote: > On Tue, Jan 12, 2016 at 10:49:57PM +0100, Arnd Bergmann wrote: > > > I see in the Armada 370 datasheet that the controller actually supports an > > interrupt driven mode, which should be much better in principle than > > blocking > > the CPU

Re: I/O issues with writing to mtdblock devices on kirkwood

2016-01-12 Thread Arnd Bergmann
On Tuesday 12 January 2016 18:02:23 Mark Brown wrote: > On Tue, Jan 12, 2016 at 05:29:40PM +0100, Arnd Bergmann wrote: > > On Tuesday 12 January 2016 02:19:04 Andrew Lunn wrote: > > > > When i played with this, i added a reschedule point at the end of the > > > drivers transfer_one_message() funct

Re: I/O issues with writing to mtdblock devices on kirkwood

2016-01-12 Thread Mark Brown
On Tue, Jan 12, 2016 at 10:49:57PM +0100, Arnd Bergmann wrote: > I see in the Armada 370 datasheet that the controller actually supports an > interrupt driven mode, which should be much better in principle than blocking > the CPU during the entire transfer. There may of course be a good reason > w

Re: I/O issues with writing to mtdblock devices on kirkwood

2016-01-12 Thread Mark Brown
On Tue, Jan 12, 2016 at 05:29:40PM +0100, Arnd Bergmann wrote: > On Tuesday 12 January 2016 02:19:04 Andrew Lunn wrote: > > When i played with this, i added a reschedule point at the end of the > > drivers transfer_one_message() function, to see if that would help. It > > did not, which is why i m

Re: I/O issues with writing to mtdblock devices on kirkwood

2016-01-12 Thread Arnd Bergmann
On Tuesday 12 January 2016 02:19:04 Andrew Lunn wrote: > > Oh, right. This sounds like everything is working fine with SPI - that > > commit was supposed to improve throughput with single threaded workloads > > by avoiding pointless context switches and it seems it is in fact doing > > that. Most

Re: Updating kernel for Debian Jessie on iMX53 QuickStart

2016-01-12 Thread Lennart Sorensen
On Mon, Jan 11, 2016 at 08:41:52PM -0800, Mike Thompson wrote: > I've got Debian Jessie armhf running on an iMX53 following the instructions > here: > > https://wiki.debian.org/InstallingDebianOn/Freescale/QuickStart > > It runs fine. However, a major issue I have is that when the kernel is > up

Re: u-boot images for OpenRD

2016-01-12 Thread Rick Thomas
On Jan 12, 2016, at 12:03 AM, Albert ARIBAUD wrote: >> Since they're building again in mainline, and we've got a few people >> interested in them, if someone can go through the trouble to file a >> wishlist bug on u-boot asking to enable them (and list themselves as a >> tester), I'll happily re

Re: u-boot images for OpenRD

2016-01-12 Thread Albert ARIBAUD
Hello Vagrant, On Mon, 11 Jan 2016 12:14:55 -0800, Vagrant Cascadian wrote: > 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