From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot PXA support
Date: Thu, 9 May 2019 16:56:20 +0200 [thread overview]
Message-ID: <99edba76-830b-2fd9-a7c1-c05bab5cf33d@denx.de> (raw)
In-Reply-To: <20190509140256.GD25571@bill-the-cat>
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 when
>> using -mcpu=xscale gcc-8.x throws an odd error:
>> cc1: error: switch -mcpu=xscale conflicts with -march=armv5te switch [-Werror]
>>
>> Now note, U-Boot isn't passing -march= at all, just -mcpu=xscale which
>> suggests perhaps something broke in upstream gcc. Looking at the
>> kernel, it's not used -mcpu=xscale ever, just -mtune=xscale but that
>> leads to different failures (seen here with gcc-7.3):
>> CC drivers/usb/gadget/pxa25x_udc.o
>> {standard input}: Assembler messages:
>> {standard input}:779: Error: selected processor does not support `pld [lr]' in ARM mode
>> {standard input}:1201: Error: selected processor does not support `pld [r7]' in ARM mode
>> {standard input}:2519: Error: selected processor does not support `pld [r3]' in ARM mode
>> {standard input}:2796: Error: selected processor does not support `pld [r3]' in ARM mode
>>
>> So, what should we do about this? Is there still active interest in
>> supporting the PXA platforms? Thanks folks!
>
> ping? Thanks!
Maybe we should just remove it.
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2019-05-09 14:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 13:26 [U-Boot] U-Boot PXA support Tom Rini
2019-05-09 14:02 ` Tom Rini
2019-05-09 14:56 ` Marek Vasut [this message]
2019-05-09 15:03 ` Vasily Khoruzhick
2019-05-09 15:12 ` Marek Vasut
2019-05-09 15:22 ` Tom Rini
2019-05-16 14:53 ` Marcel Ziswiler
2019-05-16 15:02 ` Marek Vasut
2019-05-21 8:44 ` Marcel Ziswiler
2019-05-21 9:50 ` Alex Sadovsky
2019-05-21 10:33 ` Marcel Ziswiler
2019-05-21 12:49 ` Marek Vasut
2019-05-21 14:29 ` Marcel Ziswiler
2019-05-21 14:34 ` Marek Vasut
2019-05-21 14:50 ` Tom Rini
2019-05-21 16:43 ` Simon Glass
2019-05-21 13:47 ` Tom Rini
2019-05-21 12:47 ` Marek Vasut
2019-05-21 13:47 ` Alex Sadovsky
2019-05-21 13:58 ` Tom Rini
2019-05-21 14:03 ` Marek Vasut
2019-05-21 12:51 ` Tom Rini
2019-05-16 17:49 ` Tom Rini
2019-05-17 14:46 ` Marcel Ziswiler
2019-05-29 14:12 ` Tom Rini
2019-05-30 9:14 ` Marcel Ziswiler
2019-05-30 9:29 ` Marek Vasut
2019-05-30 11:47 ` Marcel Ziswiler
2019-05-31 19:34 ` Marek Vasut
2019-05-30 10:45 ` Alex Sadovsky
2019-05-30 11:19 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99edba76-830b-2fd9-a7c1-c05bab5cf33d@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.