All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Scott <jscott@posteo.net>
To: linux-wireless@vger.kernel.org
Subject: The GNU triplet for the carl9170 firmware toolchain
Date: Tue, 19 Jan 2021 20:32:26 -0500	[thread overview]
Message-ID: <45145006.fMDQidcC6G@t450> (raw)

[-- Attachment #1: Type: text/plain, Size: 720 bytes --]

Hi,

Having been working on the same for ath9k_htc, I'm looking into making a 
Debian package for carl9170 so it gets built from source on Debian 
infrastructure. I'm trying to identify the ideal cross triplet to use for 
packaging the cross tools.

I see the toolchain Makefile builds Binutils and GCC with --target=sh-elf, but 
the README also specifies that an SH-2 toolchain is needed. Does sh-elf imply 
sh1-elf, and would it be preferable (or different) to use sh2-elf instead, or 
is it an alias for sh2-elf?

Debian already has sh4-* tools, so I'd like the parallelism of sh2-elf, but I 
wonder if this is a different ABI. config.sub seems equally happy to recognize 
either sh-elf or sh[1234]-elf.

Thanks,
John

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

                 reply	other threads:[~2021-01-20  2:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=45145006.fMDQidcC6G@t450 \
    --to=jscott@posteo.net \
    --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 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.