Hello Paul, +Menon (since you asked about the USB_OTG trap),
On 08-06-15 04:38, Paul Walmsley wrote:
Hi Jeroen,
On Sun, 7 Jun 2015, Paul Walmsley wrote:
On Sun, 7 Jun 2015, Jeroen Hofstee wrote:
Turns out my suspicion was wrong. This is what I know at the moment,
depending on the bootpins,
Hello Paul,
On 07-06-15 21:56, Paul Walmsley wrote:
On Sun, 7 Jun 2015, Jeroen Hofstee wrote:
Turns out my suspicion was wrong. This is what I know at the moment,
depending on the bootpins, u-boot will trigger a bad access when loading
a file over ethernet, but only the first time. Clearing t
Hi Jeroen,
On Sun, 7 Jun 2015, Paul Walmsley wrote:
> On Sun, 7 Jun 2015, Jeroen Hofstee wrote:
>
> > On 05-06-15 10:04, Jeroen Hofstee wrote:
> > >
> > > On 05-06-15 10:01, Jeroen Hofstee wrote:
> > > >
> > > > On 01-06-15 19:44, Paul Walmsley wrote:
> > > > > The best way to make this work I
Hi Jeroen,
On Sun, 7 Jun 2015, Jeroen Hofstee wrote:
> Hello Paul,
>
> On 05-06-15 10:04, Jeroen Hofstee wrote:
> >
> > On 05-06-15 10:01, Jeroen Hofstee wrote:
> > >
> > > On 01-06-15 19:44, Paul Walmsley wrote:
> > > > The best way to make this work IMHO would be for us not to accept any
> >
Hello Paul,
On 05-06-15 10:04, Jeroen Hofstee wrote:
On 05-06-15 10:01, Jeroen Hofstee wrote:
On 01-06-15 19:44, Paul Walmsley wrote:
The best way to make this work IMHO would be for us not to accept
any new
feature addition patches as long as there are warnings reported in the
test results
On 05-06-15 10:01, Jeroen Hofstee wrote:
Hello Paul,
On 01-06-15 19:44, Paul Walmsley wrote:
The best way to make this work IMHO would be for us not to accept any
new
feature addition patches as long as there are warnings reported in the
test results. The only real exception that I would for
Hello Paul,
On 01-06-15 19:44, Paul Walmsley wrote:
The best way to make this work IMHO would be for us not to accept any new
feature addition patches as long as there are warnings reported in the
test results. The only real exception that I would foresee is if those
warnings are due to somethi
On 06/02/2015 12:26 AM, Paul Walmsley wrote:
On Mon, 1 Jun 2015, Tony Lindgren wrote:
* Tony Lindgren [150601 11:06]:
* Paul Walmsley [150601 10:45]:
See for example the "Build warnings from toolchain", "Kernel warnings
during boot to userspace", "Kernel warnings during PM test", and "Obso
On Mon, 1 Jun 2015, Tony Lindgren wrote:
> * Tony Lindgren [150601 11:06]:
> > * Paul Walmsley [150601 10:45]:
> > >
> > > See for example the "Build warnings from toolchain", "Kernel warnings
> > > during boot to userspace", "Kernel warnings during PM test", and
> > > "Obsolete
> > > Kconfi
On Mon, 1 Jun 2015, Tony Lindgren wrote:
> * Paul Walmsley [150601 10:45]:
>
> > http://www.pwsan.com/omap/testlogs/test_v4.1-rc6/20150601012139/README.txt
>
> OK somehow 3517evm is listed under "skip" there?
Yep that board is down right now; something's wrong with it and I haven't
had the t
* Tony Lindgren [150601 11:06]:
> * Paul Walmsley [150601 10:45]:
> >
> > See for example the "Build warnings from toolchain", "Kernel warnings
> > during boot to userspace", "Kernel warnings during PM test", and "Obsolete
> > Kconfig symbols" sections here:
> >
> > http://www.pwsan.com/omap/
* Paul Walmsley [150601 10:45]:
> On Mon, 1 Jun 2015, Tony Lindgren wrote:
>
> > * Jeroen Hofstee [150601 09:58]:
> > > On 01-06-15 17:30, Tero Kristo wrote:
> > > >New system control module layout for omap3 overlooked parts of the am35xx
> > > >configuration. Basically the am35xx clocks were no
On 06/01/2015 08:44 PM, Paul Walmsley wrote:
On Mon, 1 Jun 2015, Tony Lindgren wrote:
* Jeroen Hofstee [150601 09:58]:
On 01-06-15 17:30, Tero Kristo wrote:
New system control module layout for omap3 overlooked parts of the am35xx
configuration. Basically the am35xx clocks were not converted
On Mon, 1 Jun 2015, Tony Lindgren wrote:
> * Jeroen Hofstee [150601 09:58]:
> > On 01-06-15 17:30, Tero Kristo wrote:
> > >New system control module layout for omap3 overlooked parts of the am35xx
> > >configuration. Basically the am35xx clocks were not converted to use the
> > >changed offsets,
* Jeroen Hofstee [150601 09:58]:
> Hello Tero,
>
> On 01-06-15 17:30, Tero Kristo wrote:
> >New system control module layout for omap3 overlooked parts of the am35xx
> >configuration. Basically the am35xx clocks were not converted to use the
> >changed offsets, which caused weird boot warnings. T
Hello Tero,
On 01-06-15 17:30, Tero Kristo wrote:
New system control module layout for omap3 overlooked parts of the am35xx
configuration. Basically the am35xx clocks were not converted to use the
changed offsets, which caused weird boot warnings. The errors were not
fatal so far, so they were n
New system control module layout for omap3 overlooked parts of the am35xx
configuration. Basically the am35xx clocks were not converted to use the
changed offsets, which caused weird boot warnings. The errors were not
fatal so far, so they were not caught earlier. Fixed by applying the
proper offse
17 matches
Mail list logo
