On 5/30/19 1:47 PM, Marcel Ziswiler wrote:
> On Thu, 2019-05-30 at 11:29 +0200, Marek Vasut wrote:
>> On 5/30/19 11:14 AM, Marcel Ziswiler wrote:
>>> Hi Tom
>>>
>>> On Wed, 2019-05-29 at 10:12 -0400, Tom Rini wrote:
On Thu, May 16, 2019 at 02:53:55PM +, Marcel Ziswiler wrote:
> Hi Tom
On Thu, 2019-05-30 at 11:29 +0200, Marek Vasut wrote:
> On 5/30/19 11:14 AM, Marcel Ziswiler wrote:
> > Hi Tom
> >
> > On Wed, 2019-05-29 at 10:12 -0400, Tom Rini wrote:
> > > On Thu, May 16, 2019 at 02:53:55PM +, Marcel Ziswiler wrote:
> > > > Hi Tom
> > > >
> > > > On Mon, 2019-05-06 at
On Thu, May 30, 2019 at 01:45:22PM +0300, Alex Sadovsky wrote:
> > - HP iPAQ Pocket PC h2200
> >
> > A consumer device with PXA255 from back in 2002. There has not been any
> > activity on h2200 from its maintainer Lukasz Dalek for almost 5 years
> > now. Without anybody actually owning such
> - HP iPAQ Pocket PC h2200
>
> A consumer device with PXA255 from back in 2002. There has not been any
> activity on h2200 from its maintainer Lukasz Dalek for almost 5 years
> now. Without anybody actually owning such hardware stepping up it will
> be quite impossible to maintain.
I still have
On 5/30/19 11:14 AM, Marcel Ziswiler wrote:
> Hi Tom
>
> On Wed, 2019-05-29 at 10:12 -0400, Tom Rini wrote:
>> On Thu, May 16, 2019 at 02:53:55PM +, Marcel Ziswiler wrote:
>>> Hi Tom
>>>
>>> On Mon, 2019-05-06 at 09:26 -0400, Tom Rini wrote:
Hey folks,
I'm attempting, again, to
Hi Tom
On Wed, 2019-05-29 at 10:12 -0400, Tom Rini wrote:
> On Thu, May 16, 2019 at 02:53:55PM +, Marcel Ziswiler wrote:
> > Hi Tom
> >
> > On Mon, 2019-05-06 at 09:26 -0400, Tom Rini wrote:
> > > Hey folks,
> > >
> > > I'm attempting, again, to see what we need to do in order to use
> > >
On Thu, May 16, 2019 at 02:53:55PM +, Marcel Ziswiler wrote:
> Hi Tom
>
> On Mon, 2019-05-06 at 09:26 -0400, Tom Rini wrote:
> > Hey folks,
> >
> > I'm attempting, again, to see what we need to do in order to use gcc-
> > 8.x
> > for U-Boot and ran into, again:
> >
Hi,
On Tue, 21 May 2019 at 08:50, Tom Rini wrote:
>
> On Tue, May 21, 2019 at 04:34:19PM +0200, Marek Vasut wrote:
> > On 5/21/19 4:29 PM, Marcel Ziswiler wrote:
> > > On Tue, 2019-05-21 at 14:49 +0200, Marek Vasut wrote:
> > >> On 5/21/19 12:33 PM, Marcel Ziswiler wrote:
> > >>> On Tue,
On Tue, May 21, 2019 at 04:34:19PM +0200, Marek Vasut wrote:
> On 5/21/19 4:29 PM, Marcel Ziswiler wrote:
> > On Tue, 2019-05-21 at 14:49 +0200, Marek Vasut wrote:
> >> On 5/21/19 12:33 PM, Marcel Ziswiler wrote:
> >>> On Tue, 2019-05-21 at 12:50 +0300, Alex Sadovsky wrote:
> It's slightly
On 5/21/19 4:29 PM, Marcel Ziswiler wrote:
> On Tue, 2019-05-21 at 14:49 +0200, Marek Vasut wrote:
>> On 5/21/19 12:33 PM, Marcel Ziswiler wrote:
>>> On Tue, 2019-05-21 at 12:50 +0300, Alex Sadovsky wrote:
It's slightly off-topic but I wonder whether this ongoing
deprecation
of
On Tue, 2019-05-21 at 14:49 +0200, Marek Vasut wrote:
> On 5/21/19 12:33 PM, Marcel Ziswiler wrote:
> > On Tue, 2019-05-21 at 12:50 +0300, Alex Sadovsky wrote:
> > > It's slightly off-topic but I wonder whether this ongoing
> > > deprecation
> > > of ARMv4 and ARMv5 (first in GCC, then in U-Boot)
On 5/21/19 3:47 PM, Alex Sadovsky wrote:
> On 21/05/2019, Marek Vasut wrote:
>> On 5/21/19 11:50 AM, Alex Sadovsky wrote:
>>> It's slightly off-topic but I wonder whether this ongoing deprecation
>>> of ARMv4 and ARMv5 (first in GCC, then in U-Boot) really simplifies
>>> anything at all.
>>>
On Tue, May 21, 2019 at 04:47:44PM +0300, Alex Sadovsky wrote:
> On 21/05/2019, Marek Vasut wrote:
> > On 5/21/19 11:50 AM, Alex Sadovsky wrote:
> >> It's slightly off-topic but I wonder whether this ongoing deprecation
> >> of ARMv4 and ARMv5 (first in GCC, then in U-Boot) really simplifies
> >>
On 21/05/2019, Marek Vasut wrote:
> On 5/21/19 11:50 AM, Alex Sadovsky wrote:
>> It's slightly off-topic but I wonder whether this ongoing deprecation
>> of ARMv4 and ARMv5 (first in GCC, then in U-Boot) really simplifies
>> anything at all.
>> There are tons of devices that are still working
On Tue, May 21, 2019 at 10:33:39AM +, Marcel Ziswiler wrote:
> On Tue, 2019-05-21 at 12:50 +0300, Alex Sadovsky wrote:
> > It's slightly off-topic but I wonder whether this ongoing deprecation
> > of ARMv4 and ARMv5 (first in GCC, then in U-Boot) really simplifies
> > anything at all.
> >
On 5/21/19 11:50 AM, Alex Sadovsky wrote:
> It's slightly off-topic but I wonder whether this ongoing deprecation
> of ARMv4 and ARMv5 (first in GCC, then in U-Boot) really simplifies
> anything at all.
> There are tons of devices that are still working good and there are
> even ARMv5-based MCUs
On 5/21/19 12:33 PM, Marcel Ziswiler wrote:
> On Tue, 2019-05-21 at 12:50 +0300, Alex Sadovsky wrote:
>> It's slightly off-topic but I wonder whether this ongoing deprecation
>> of ARMv4 and ARMv5 (first in GCC, then in U-Boot) really simplifies
>> anything at all.
>> There are tons of devices
On Tue, May 21, 2019 at 08:44:57AM +, Marcel Ziswiler wrote:
> On Thu, 2019-05-16 at 17:02 +0200, Marek Vasut wrote:
> > On 5/16/19 4:53 PM, Marcel Ziswiler wrote:
> > > Hi Tom
> > >
> > > On Mon, 2019-05-06 at 09:26 -0400, Tom Rini wrote:
> > > > Hey folks,
> > > >
> > > > I'm attempting,
On Tue, 2019-05-21 at 12:50 +0300, Alex Sadovsky wrote:
> It's slightly off-topic but I wonder whether this ongoing deprecation
> of ARMv4 and ARMv5 (first in GCC, then in U-Boot) really simplifies
> anything at all.
> There are tons of devices that are still working good and there are
> even
It's slightly off-topic but I wonder whether this ongoing deprecation
of ARMv4 and ARMv5 (first in GCC, then in U-Boot) really simplifies
anything at all.
There are tons of devices that are still working good and there are
even ARMv5-based MCUs that are still produced (such as CH561
manufactured
On Thu, 2019-05-16 at 17:02 +0200, Marek Vasut wrote:
> On 5/16/19 4:53 PM, Marcel Ziswiler wrote:
> > Hi Tom
> >
> > On Mon, 2019-05-06 at 09:26 -0400, Tom Rini wrote:
> > > Hey folks,
> > >
> > > I'm attempting, again, to see what we need to do in order to use
> > > gcc-
> > > 8.x
> > > for
On Thu, 2019-05-16 at 13:49 -0400, Tom Rini wrote:
> On Thu, May 16, 2019 at 02:53:55PM +, Marcel Ziswiler wrote:
> > Hi Tom
> >
> > On Mon, 2019-05-06 at 09:26 -0400, Tom Rini wrote:
> > > Hey folks,
> ...
> > > So, what should we do about this? Is there still active interest
> > > in
> > >
On Thu, May 16, 2019 at 02:53:55PM +, Marcel Ziswiler wrote:
> Hi Tom
>
> On Mon, 2019-05-06 at 09:26 -0400, Tom Rini wrote:
> > Hey folks,
> >
> > I'm attempting, again, to see what we need to do in order to use gcc-
> > 8.x
> > for U-Boot and ran into, again:
> >
On 5/16/19 4:53 PM, Marcel Ziswiler wrote:
> Hi Tom
>
> On Mon, 2019-05-06 at 09:26 -0400, Tom Rini wrote:
>> Hey folks,
>>
>> I'm attempting, again, to see what we need to do in order to use gcc-
>> 8.x
>> for U-Boot and ran into, again:
>> https://patchwork.ozlabs.org/patch/920329/ which in
Hi Tom
On Mon, 2019-05-06 at 09:26 -0400, Tom Rini wrote:
> Hey folks,
>
> I'm attempting, again, to see what we need to do in order to use gcc-
> 8.x
> for U-Boot and ran into, again:
> https://patchwork.ozlabs.org/patch/920329/ which in short is that
> when
> using -mcpu=xscale gcc-8.x throws
On Thu, May 09, 2019 at 05:12:25PM +0200, Marek Vasut wrote:
> On 5/9/19 5:03 PM, Vasily Khoruzhick wrote:
> > On Thu, May 9, 2019 at 7:56 AM Marek Vasut wrote:
> >>
> >> On 5/9/19 4:02 PM, Tom Rini wrote:
> >>> On Mon, May 06, 2019 at 09:26:04AM -0400, Tom Rini wrote:
> >>>
> Hey folks,
>
On 5/9/19 5:03 PM, Vasily Khoruzhick wrote:
> On Thu, May 9, 2019 at 7:56 AM Marek Vasut wrote:
>>
>> On 5/9/19 4:02 PM, Tom Rini wrote:
>>> On Mon, May 06, 2019 at 09:26:04AM -0400, Tom Rini wrote:
>>>
Hey folks,
I'm attempting, again, to see what we need to do in order to use
On Thu, May 9, 2019 at 7:56 AM Marek Vasut wrote:
>
> On 5/9/19 4:02 PM, Tom Rini wrote:
> > On Mon, May 06, 2019 at 09:26:04AM -0400, Tom Rini wrote:
> >
> >> Hey folks,
> >>
> >> I'm attempting, again, to see what we need to do in order to use gcc-8.x
> >> for U-Boot and ran into, again:
> >>
On 5/9/19 4:02 PM, Tom Rini wrote:
> On Mon, May 06, 2019 at 09:26:04AM -0400, Tom Rini wrote:
>
>> Hey folks,
>>
>> I'm attempting, again, to see what we need to do in order to use gcc-8.x
>> for U-Boot and ran into, again:
>> https://patchwork.ozlabs.org/patch/920329/ which in short is that
On Mon, May 06, 2019 at 09:26:04AM -0400, Tom Rini wrote:
> Hey folks,
>
> I'm attempting, again, to see what we need to do in order to use gcc-8.x
> for U-Boot and ran into, again:
> https://patchwork.ozlabs.org/patch/920329/ which in short is that when
> using -mcpu=xscale gcc-8.x throws an
Hey folks,
I'm attempting, again, to see what we need to do in order to use gcc-8.x
for U-Boot and ran into, again:
https://patchwork.ozlabs.org/patch/920329/ which in short is that when
using -mcpu=xscale gcc-8.x throws an odd error:
cc1: error: switch -mcpu=xscale conflicts with -march=armv5te
31 matches
Mail list logo
