Hi,
On 6.01.2016 20:26, Tony Lindgren wrote:
Hmm. Care to verify that your onenand really gets detected at 83 MHz like
your earlier logs show? Below is a patch that should show it.
before the corruption appeared, I looked a couple of times in syslog and
the freq there was 83MHz. Including
* Ivaylo Dimitrov [160106 10:01]:
>
> Unfortunately, it seems there is more to be fixed. It booted several times
> to the userspace, but after a couple of shutdowns, rootfs became corrupted
> again. I flashed, installed linux 4.4, but the same happened after the first
> shutdown with 4.4:
Hmm. C
On 6.01.2016 19:47, Tony Lindgren wrote:
* Sebastian Reichel [160106 09:41]:
Hi,
On Tue, Jan 05, 2016 at 02:49:29PM -0800, Tony Lindgren wrote:
Commit 63aa945b1013 ("memory: omap-gpmc: Add Kconfig option for debug")
unified the GPMC debug for the SoCs with GPMC. The commit also left
out th
* Sebastian Reichel [160106 09:41]:
> Hi,
>
> On Tue, Jan 05, 2016 at 02:49:29PM -0800, Tony Lindgren wrote:
> > Commit 63aa945b1013 ("memory: omap-gpmc: Add Kconfig option for debug")
> > unified the GPMC debug for the SoCs with GPMC. The commit also left
> > out the option for HWMOD_INIT_NO_RES
Hi,
On Tue, Jan 05, 2016 at 02:49:29PM -0800, Tony Lindgren wrote:
> Commit 63aa945b1013 ("memory: omap-gpmc: Add Kconfig option for debug")
> unified the GPMC debug for the SoCs with GPMC. The commit also left
> out the option for HWMOD_INIT_NO_RESET as we now require proper timings
> for GPMC to
Hi,
On Tue, Jan 05, 2016 at 02:49:29PM -0800, Tony Lindgren wrote:
> From: Tony Lindgren
> Date: Tue, 5 Jan 2016 12:04:20 -0800
> Subject: [PATCH] ARM: OMAP2+: Fix onenand rate detection to avoid filesystem
> corruption
>
> Commit 63aa945b1013 ("memory: omap-gpmc: Add Kconfig option for debug")
* Pali Rohár [160106 01:06]:
> On Wednesday 06 January 2016 10:55:51 Ivaylo Dimitrov wrote:
> > On 6.01.2016 00:49, Tony Lindgren wrote:
> > >
> > >Suggested fix below, please test and reply with your Tested-by's if
> > >it solves the problem so we may still be able to get this into v4.4.
> > >
>
On Wednesday 06 January 2016 10:55:51 Ivaylo Dimitrov wrote:
>
>
> On 6.01.2016 00:49, Tony Lindgren wrote:
> >
> >Suggested fix below, please test and reply with your Tested-by's if
> >it solves the problem so we may still be able to get this into v4.4.
> >
> >Regards,
> >
> >Tony
> >
> >8< ---
On 6.01.2016 00:49, Tony Lindgren wrote:
Suggested fix below, please test and reply with your Tested-by's if
it solves the problem so we may still be able to get this into v4.4.
Regards,
Tony
8< ---
From: Tony Lindgren
Date: Tue, 5 Jan 2016 12:04:20 -0800
Subject: [PATCH] ARM:
* Pali Rohár [160105 00:50]:
> On Monday 04 January 2016 20:13:56 Tony Lindgren wrote:
> > * Ivaylo Dimitrov [160104 10:59]:
> > > Hi,
> > >
> > > On 4.01.2016 19:40, Tony Lindgren wrote:
> > > >>On Monday 04 January 2016 18:02:06 Tony Lindgren wrote:
> > > >Care to boot with CONFIG_OMAP_G
On Monday 04 January 2016 20:13:56 Tony Lindgren wrote:
> * Ivaylo Dimitrov [160104 10:59]:
> > Hi,
> >
> > On 4.01.2016 19:40, Tony Lindgren wrote:
> > >>On Monday 04 January 2016 18:02:06 Tony Lindgren wrote:
> > >Care to boot with CONFIG_OMAP_GPMC_DEBUG=y and post the gpmc related
> > >>
* Ivaylo Dimitrov [160104 10:59]:
> Hi,
>
> On 4.01.2016 19:40, Tony Lindgren wrote:
> >>On Monday 04 January 2016 18:02:06 Tony Lindgren wrote:
> >Care to boot with CONFIG_OMAP_GPMC_DEBUG=y and post the gpmc related
> >dmesg output?
>
> Here it is, including the pre-gpmc log, keep in
Hi,
On 4.01.2016 19:40, Tony Lindgren wrote:
On Monday 04 January 2016 18:02:06 Tony Lindgren wrote:
> >Care to boot with CONFIG_OMAP_GPMC_DEBUG=y and post the gpmc related
> >dmesg output?
Here it is, including the pre-gpmc log, keep in mind this is with
restored HWMOD_INIT_NO_RESET flag s
* Pali Rohár [160104 09:35]:
> On Monday 04 January 2016 18:02:06 Tony Lindgren wrote:
> > Care to boot with CONFIG_OMAP_GPMC_DEBUG=y and post the gpmc related
> > dmesg output?
>
> Hi Tony. We do not have serial console for N900 and so when kernel is
> not fully bootable to userspace we cannot
On Monday 04 January 2016 18:02:06 Tony Lindgren wrote:
> Care to boot with CONFIG_OMAP_GPMC_DEBUG=y and post the gpmc related
> dmesg output?
Hi Tony. We do not have serial console for N900 and so when kernel is
not fully bootable to userspace we cannot provide dmesg for you :-(
Maybe something
* Ivaylo Dimitrov [160101 03:29]:
> Hi Tony,
>
> On 21.05.2015 00:21, Tony Lindgren wrote:
> >We support decoding the bootloader values if DEBUG is defined.
> >But we also need to change the struct omap_hwmod flags to have
> >HWMOD_INIT_NO_RESET to avoid the GPMC being reset during the
> >boot. O
Hi Tony,
On 21.05.2015 00:21, Tony Lindgren wrote:
We support decoding the bootloader values if DEBUG is defined.
But we also need to change the struct omap_hwmod flags to have
HWMOD_INIT_NO_RESET to avoid the GPMC being reset during the
boot. Otherwise just the default timings will be displayed
On 01/09/15 16:31, Hannes Schmelzer wrote:
>> Hi Hannes,
> Hi Roger,
>
>>
>> On 27/08/15 08:52, Hannes Schmelzer wrote:
>>> Hi Tony,
>>>
>>> Did anyone test this changeset on some AM335x board?
>>>
>>> Today I ran into trouble with that because:
>>>
>>> The GPMC controller gets reseted on kernel b
> Hi Hannes,
Hi Roger,
>
> On 27/08/15 08:52, Hannes Schmelzer wrote:
> > Hi Tony,
> >
> > Did anyone test this changeset on some AM335x board?
> >
> > Today I ran into trouble with that because:
> >
> > The GPMC controller gets reseted on kernel boot due to the
missing/removed
> HWMOD_INIT_
Hi Hannes,
On 27/08/15 08:52, Hannes Schmelzer wrote:
> Hi Tony,
>
> Did anyone test this changeset on some AM335x board?
>
> Today I ran into trouble with that because:
>
> The GPMC controller gets reseted on kernel boot due to the missing/removed
> HWMOD_INIT_NO_RESET flag.
>
> Primary this
Hi Hannes,
On 27/08/15 08:52, Hannes Schmelzer wrote:
> Hi Tony,
>
> Did anyone test this changeset on some AM335x board?
>
> Today I ran into trouble with that because:
>
> The GPMC controller gets reseted on kernel boot due to the missing/removed
> HWMOD_INIT_NO_RESET flag.
>
> Primary this
>
> Hi,
Hi,
>
> * Hannes Schmelzer [150826 22:55]:
> > Hi Tony,
> >
> > Did anyone test this changeset on some AM335x board?
>
> Apparently not if it does not work or else you somehow have a different
> configuration for GPMC.
>
> > Today I ran into trouble with that because:
> >
> > The GP
Hi,
* Hannes Schmelzer [150826 22:55]:
> Hi Tony,
>
> Did anyone test this changeset on some AM335x board?
Apparently not if it does not work or else you somehow have a different
configuration for GPMC.
> Today I ran into trouble with that because:
>
> The GPMC controller gets reseted on ker
Hi Tony,
Did anyone test this changeset on some AM335x board?
Today I ran into trouble with that because:
The GPMC controller gets reseted on kernel boot due to the missing/removed
HWMOD_INIT_NO_RESET flag.
Primary this should not be a big problem, but on my board (maybe on all
AM335x) the GP
On Wed, 20 May 2015, Tony Lindgren wrote:
> * Paul Walmsley [150520 15:52]:
> > On Wed, 20 May 2015, Tony Lindgren wrote:
> >
> > > We support decoding the bootloader values if DEBUG is defined.
> > > But we also need to change the struct omap_hwmod flags to have
> > > HWMOD_INIT_NO_RESET to avo
* Paul Walmsley [150520 15:52]:
> On Wed, 20 May 2015, Tony Lindgren wrote:
>
> > We support decoding the bootloader values if DEBUG is defined.
> > But we also need to change the struct omap_hwmod flags to have
> > HWMOD_INIT_NO_RESET to avoid the GPMC being reset during the
> > boot. Otherwise
On Wed, 20 May 2015, Tony Lindgren wrote:
> We support decoding the bootloader values if DEBUG is defined.
> But we also need to change the struct omap_hwmod flags to have
> HWMOD_INIT_NO_RESET to avoid the GPMC being reset during the
> boot. Otherwise just the default timings will be displayed
>
27 matches
Mail list logo