On Tue, Jul 05, 2016 at 10:52:37AM +0200, Ben Hutchings wrote:
> On Tue, 2016-07-05 at 10:07 +0200, Mark Brown wrote:
> > We're getting to the point where there's a fairly pressing need for
> > arm64 - the more useful hardware is starting to get a wider distribution
>
On Mon, Jul 04, 2016 at 07:05:42PM +0200, Ben Hutchings wrote:
> On Mon, 2016-07-04 at 14:01 +0100, Steve McIntyre wrote:
> > A lot of arm64 machine users would benefit from this, and maybe owners
> > of very recent amd64 machines too, with better support for things on
> > the Skylake platform. Th
On Tue, Jan 12, 2016 at 11:41:45PM +0100, Arnd Bergmann wrote:
> On Tuesday 12 January 2016 22:00:58 Mark Brown wrote:
> > There's also the potential for the overhead from interrupts to be worse
> > than the overhead for busy waiting, but given how badly we're coping n
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
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
On Tue, Jan 12, 2016 at 02:19:04AM +0100, 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 made a guess it has something to do with a
> lock.
The SPI core d
On Tue, Jan 12, 2016 at 12:43:37AM +0100, Andrew Lunn wrote:
> I've done a little testing. What appears to happen is that while the
> cat file > /dev/mtdblockX is going on, all access to filesystems on
> SATA are blocked. I set off a "find ." and it busily prints
> filenames. But as soon as i star
On Mon, Jan 11, 2016 at 04:07:21PM -0800, Martin Michlmayr wrote:
> * Mark Brown [2016-01-11 23:22]:
I've just noticed that you're asking about the kernel SPI subsystem on
the Debian ARM list, please don't do things like this - please include
the kernel community, you'll b
/dev/mtdblockX worked fine on a 2 MB flash partition but
> resulted in SATA timeouts on a 9 MB flash partition.
> flascp file /dev/mtd2 works fine.
> I've now bisected it down to this change:
> commit 0461a4149836c792d186027c8c859637a4cfb11a
> Author: Mark Brown
>
On Mon, Sep 16, 2013 at 10:11:47AM +0200, Arnaud Patard wrote:
> exynos in armmp won't happen anytime soon unless you bug upstream about
> multiplatform support. iirc, even in -next, it's still not possible to
> enable exynos in multiplatform builds.
It does mostly work with mainline, audio still
On Tue, Aug 20, 2013 at 01:39:40AM +0200, Ben Hutchings wrote:
> On Mon, 2013-08-19 at 11:41 +0100, Mark Brown wrote:
> > Could you be more specific as to what you believe the problem that
> > exists is? You mentioned that the kernel would be tainted but that
> > doesn'
On Sat, Aug 17, 2013 at 06:25:44PM +0200, Ben Hutchings wrote:
> On Fri, 2013-08-16 at 11:34 +0100, Mark Brown wrote:
> > Please use the advertised e-mail addresses for maintainers.
> Expand, please? I took your address from the commit that Robert pointed
> out.
You
On 16 August 2013 09:42, Ben Hutchings wrote:
Please use the advertised e-mail addresses for maintainers.
On Thu, 2013-08-15 at 19:16 -0500, Robert Nelson wrote:
> > This is fixed in the sound next branch:
> >
> >
> https://git.kernel.org/cgit/linux/kernel/git/broonie/sound.git/commit/?h=for-nex
On Thu, Jun 06, 2013 at 02:01:14AM +0200, Tomasz Figa wrote:
> I don't see any other solution here than moving all the Allwinner code to
> DT (as it has been suggested in this thread several times already), as
> this is the only hardware description method supported by ARM Linux.
Well, the serv
On Mon, Mar 01, 2010 at 12:52:11PM +0100, Marcus Better wrote:
> Luke Kenneth Casson Leighton wrote:
> > next interesting things to try include recompiling and replacing
> > xserver-xorg with kdrive, why the hell isn't there a debian package
> > for kdrive??
> Guessing: because there is xserver-x
On Sat, Aug 01, 2009 at 08:19:37PM +0100, Andrew M.A. Cater wrote:
> USB 0: host mode
> PEX 0: interface detected no Link.
> Net: egiga0 [PRIME], egiga1
> Hit any key to stop autoboot: 0
> Using egiga0 device
> TFTP from server 10.4.50.5; our IP address is 10.4.50.165
> Filename 'uImage'.
> Loa
On Thu, Nov 13, 2008 at 04:43:20PM +0200, Riku Voipio wrote:
> I believe Current status is that basic OMAP3 and some OMAP2 support
> is in mainline kernel now. The biggest bit missing ATM is the
> TWL4030 driver. And then the big stream of power managment stuff
> that is still WiP...
TWL4030 seem
On Thu, Nov 13, 2008 at 02:22:21PM +0100, Martin Michlmayr wrote:
> I actually read about the new Gumstix in LWN today which is also OMAP
> based. The Gumstix and Beagleboard definitely sound interesting.
> Maybe we can TI to donate some.
It'd be good, yes. Though at the price of the beagleboar
On Wed, Nov 12, 2008 at 11:31:50PM +0100, Martin Michlmayr wrote:
> too long to build. So you'd have to come up with a good argument as
> to why we should add an OMAP kernel (e.g. how many users are there
> going to be; which devices use such a CPU, etc).
The Beagleboard and other platforms deri
19 matches
Mail list logo
