linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <linux@rempel-privat.de>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: ath9k-devel@qca.qualcomm.com,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	ath10k@lists.infradead.org
Subject: Re: Search for devices with Xtensa cores
Date: Sat, 20 May 2017 13:02:35 +0200	[thread overview]
Message-ID: <1855b2ff-3ed0-a2c3-ad27-7971fa92ee98@rempel-privat.de> (raw)
In-Reply-To: <CAMo8Bf+xbS46Kj4VP_+F2aZPZpOJ2UHV6WdHP_Ku_eaSQwm-7g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1464 bytes --]

Am 16.05.2017 um 21:46 schrieb Max Filippov:
> HI Oleksij,
> 
> On Fri, Apr 28, 2017 at 11:23 PM, Oleksij Rempel <linux@rempel-privat.de> wrote:
>> this year started with inclusion of open-ath9k-htc-firmware to debian
>> *main* repository. As first we started to getting advantage of regular
>> compile tests. See results here:
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/open-ath9k-htc-firmware.html
>>
>> Most of the problems which we currently get, are related to gcc xtensa
>> compiler.
>> In details: device specific patch set is used to provide our own
>> gcc/binutils version because Xtensa don't really have defined CPU cores.
>> As result, upstream compiler developers will never notice if some thing
>> will brake this patch set.
> 
> Below are the links to the xtensa-dynconfig repository and xtensa-plugin-env
> branches in binutils-gdb and gcc repositories. Together it is a draft
> implementation of dynamically configurable xtensa toolchain.
> Could you please take a look at it and see if it's useful for you?
> 
> https://github.com/jcmvbkbc/xtensa-dynconfig
> https://github.com/jcmvbkbc/binutils-gdb-xtensa/commits/xtensa-plugin-env
> https://github.com/jcmvbkbc/gcc-xtensa/commits/xtensa-plugin-env

I didn't tested it jet, but it looks promising. How can i itegrate this
two patches?
https://github.com/olerem/open-ath9k-htc-firmware/tree/master/local/patches


-- 
Regards,
Oleksij


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-05-20 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29  6:23 Search for devices with Xtensa cores Oleksij Rempel
2017-05-16 19:46 ` Max Filippov
2017-05-20 11:02   ` Oleksij Rempel [this message]
2017-05-21  4:47     ` Max Filippov

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=1855b2ff-3ed0-a2c3-ad27-7971fa92ee98@rempel-privat.de \
    --to=linux@rempel-privat.de \
    --cc=ath10k@lists.infradead.org \
    --cc=ath9k-devel@qca.qualcomm.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).