* Nicolas Pitre [110419 06:24]:
> On Tue, 19 Apr 2011, Tony Lindgren wrote:
>
> > Aaro and I speculated that boards using u-boot with uImage work,
> > while n900 is using zImage and fails with the same kernel probably
> > because of the different placement of compressed image in the
> > memory.
>
On Tue, 19 Apr 2011, Tony Lindgren wrote:
> Aaro and I speculated that boards using u-boot with uImage work,
> while n900 is using zImage and fails with the same kernel probably
> because of the different placement of compressed image in the
> memory.
Could you try the following (by changing the
* Tony Lindgren [110413 08:06]:
> * Nicolas Pitre [110413 17:46]:
> > On Wed, 13 Apr 2011, Tony Lindgren wrote:
> > >
> > > With the device tree append patch reverting commit
> > > d239b1dc093d551046a909920b5310c1d1e308c1 does not help, and reverting
> > > 6d7d0ae51574943bf571d269da3243257a2d15d
On Wed, 13 Apr 2011 17:34:24 +0300 (EEST)
Aaro Koskinen wrote:
> > Aaro, you mentioned to me that reverting commit
> > 6d7d0ae51574943bf571d269da3243257a2d15db helps too?
> >
> > With the device tree append patch reverting commit
> > d239b1dc093d551046a909920b5310c1d1e308c1 does not help, and rev
* Nicolas Pitre [110413 17:46]:
> On Wed, 13 Apr 2011, Tony Lindgren wrote:
> >
> > With the device tree append patch reverting commit
> > d239b1dc093d551046a909920b5310c1d1e308c1 does not help, and reverting
> > 6d7d0ae51574943bf571d269da3243257a2d15db requires some manual merging..
>
> You can
On Wed, 13 Apr 2011, Tony Lindgren wrote:
> * Nicolas Pitre [110402 05:40]:
> > On Thu, 31 Mar 2011, Aaro Koskinen wrote:
> >
> > > Hi,
> > >
> > > On Wed, 30 Mar 2011, Kevin Hilman wrote:
> > > > Tony Lindgren writes:
> > > > > FYI, looks like we've started hitting some booter -l kernel size
Hi,
On Wed, 13 Apr 2011, Tony Lindgren wrote:
* Nicolas Pitre [110402 05:40]:
On Thu, 31 Mar 2011, Aaro Koskinen wrote:
On Wed, 30 Mar 2011, Kevin Hilman wrote:
Tony Lindgren writes:
FYI, looks like we've started hitting some booter -l kernel size limit
in addition to booter -f size limit.
* Nicolas Pitre [110402 05:40]:
> On Thu, 31 Mar 2011, Aaro Koskinen wrote:
>
> > Hi,
> >
> > On Wed, 30 Mar 2011, Kevin Hilman wrote:
> > > Tony Lindgren writes:
> > > > FYI, looks like we've started hitting some booter -l kernel size limit
> > > > in addition to booter -f size limit.. Now ker
On Thu, 31 Mar 2011, Aaro Koskinen wrote:
> Hi,
>
> On Wed, 30 Mar 2011, Kevin Hilman wrote:
> > Tony Lindgren writes:
> > > FYI, looks like we've started hitting some booter -l kernel size limit
> > > in addition to booter -f size limit.. Now kernels built with
> > > omap2plus_defconfig won't b
Hi,
On Wed, 30 Mar 2011, Kevin Hilman wrote:
Tony Lindgren writes:
FYI, looks like we've started hitting some booter -l kernel size limit
in addition to booter -f size limit.. Now kernels built with
omap2plus_defconfig won't boot on n900 any longer.
I guess you are seeing it just hanging at
Tony Lindgren writes:
> * Aaro Koskinen [110316 10:10]:
>>
>> Somehow I figured this out, the patch "arm: mach-omap2: omap_l3_smx:
>> fix irq handler setup" fixes the hang for me (and of course I still need
>> to comment out timer 12).
>
> FYI, looks like we've started hitting some booter -l ke
* Aaro Koskinen [110316 10:10]:
>
> Somehow I figured this out, the patch "arm: mach-omap2: omap_l3_smx:
> fix irq handler setup" fixes the hang for me (and of course I still need
> to comment out timer 12).
FYI, looks like we've started hitting some booter -l kernel size limit
in addition to bo
Hi,
On Wed, 16 Mar 2011, Tony Lindgren wrote:
FYI, my rx51 boots fine with omap2plus defconfig, also with
earlyprintk.
For the RX-51 earlyprintk problem I need to enable pr_debug()s in
omap_hwmod.c. Otherwise it won't trigger. Of course that's a pretty
artificial test case, so I guess we can f
Hi,
On Wed, 16 Mar 2011, Cousson, Benoit wrote:
On 3/16/2011 2:49 PM, Aaro Koskinen wrote:
On Tue, 15 Mar 2011, Cousson, Benoit wrote:
Mmm, that looks like an access to a secure timer from hwmod code on a HS
device. Could you comment out the timer12 entry (&omap3xxx_timer12_hwmod)
in
the oma
* Cousson, Benoit [110316 07:31]:
> Hi Aaro,
>
> On 3/16/2011 2:49 PM, Aaro Koskinen wrote:
> >Hi,
> >
> >On Tue, 15 Mar 2011, Cousson, Benoit wrote:
> >>Mmm, that looks like an access to a secure timer from hwmod code on a HS
> >>device. Could you comment out the timer12 entry (&omap3xxx_timer12
On Wed, Mar 16, 2011 at 7:50 PM, G, Manjunath Kondaiah wrote:
> On Wed, Mar 16, 2011 at 07:37:10PM +0530, G, Manjunath Kondaiah wrote:
>> On Mon, Mar 14, 2011 at 12:25:38PM -0700, Tony Lindgren wrote:
>> > Hi all,
>> >
>> > I've applied few random fix like patches today into omap-for-linus
>> > bu
Hi Aaro,
On 3/16/2011 2:49 PM, Aaro Koskinen wrote:
Hi,
On Tue, 15 Mar 2011, Cousson, Benoit wrote:
Mmm, that looks like an access to a secure timer from hwmod code on a HS
device. Could you comment out the timer12 entry (&omap3xxx_timer12_hwmod) in
the omap3 hwmod list at the end of omap_hwmo
On Wed, Mar 16, 2011 at 07:37:10PM +0530, G, Manjunath Kondaiah wrote:
> On Mon, Mar 14, 2011 at 12:25:38PM -0700, Tony Lindgren wrote:
> > Hi all,
> >
> > I've applied few random fix like patches today into omap-for-linus
> > but that's it for this merge window.
> >
> > So let's do some testing
On Mon, Mar 14, 2011 at 12:25:38PM -0700, Tony Lindgren wrote:
> Hi all,
>
> I've applied few random fix like patches today into omap-for-linus
> but that's it for this merge window.
>
> So let's do some testing with with Stephen's for-next and
> omap-for-linus and start queueing up fixes for the
Hi,
On Tue, 15 Mar 2011, Cousson, Benoit wrote:
Mmm, that looks like an access to a secure timer from hwmod code on a HS
device. Could you comment out the timer12 entry (&omap3xxx_timer12_hwmod) in
the omap3 hwmod list at the end of omap_hwmod_3xxx_data.c to check that?
With timer12 entry com
Hi,
From: Cousson, Benoit [b-cous...@ti.com]:
>On 3/15/2011 6:54 PM, Aaro Koskinen wrote:
>> On Mon, 14 Mar 2011, Tony Lindgren wrote:
>>> I've applied few random fix like patches today into omap-for-linus
>>> but that's it for this merge window.
>>>
>>> So let's do some testing with with Stephen'
Hi Aaro,
On 3/15/2011 6:54 PM, Aaro Koskinen wrote:
Hi,
On Mon, 14 Mar 2011, Tony Lindgren wrote:
I've applied few random fix like patches today into omap-for-linus
but that's it for this merge window.
So let's do some testing with with Stephen's for-next and
omap-for-linus and start queueing
Hi,
On Mon, 14 Mar 2011, Tony Lindgren wrote:
I've applied few random fix like patches today into omap-for-linus
but that's it for this merge window.
So let's do some testing with with Stephen's for-next and
omap-for-linus and start queueing up fixes for the -rc cycle.
I did some quick testin
On Tue, Mar 15, 2011 at 20:39, Kevin Hilman wrote:
> Nishanth Menon writes:
>
>> Tony Lindgren wrote, on 03/15/2011 12:55 AM:
>> [..]
>>> Looks like there's one smartreflex patch that does not seem
>>> to exist in patchwork though.. So that one is still lurking
>>> around on the patchwork list of
Nishanth Menon writes:
> Tony Lindgren wrote, on 03/15/2011 12:55 AM:
> [..]
>> Looks like there's one smartreflex patch that does not seem
>> to exist in patchwork though.. So that one is still lurking
>> around on the patchwork list of patches until the issue has
>> been fixed in patchwork.kern
Tony Lindgren wrote, on 03/15/2011 12:55 AM:
[..]
Looks like there's one smartreflex patch that does not seem
to exist in patchwork though.. So that one is still lurking
around on the patchwork list of patches until the issue has
been fixed in patchwork.kernel.org.
Guess it is too late, but am c
Hi all,
I've applied few random fix like patches today into omap-for-linus
but that's it for this merge window.
So let's do some testing with with Stephen's for-next and
omap-for-linus and start queueing up fixes for the -rc cycle.
I've also moved all the patchwork.kernel.org patches into
archiv
27 matches
Mail list logo
