public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <binutils@emagii.com>
To: binutils@sourceware.org
Cc: nickc@redhat.com
Subject: Re: [PATCH v1 0/3 CHIP: Support vendor script libraries
Date: Tue, 14 Mar 2023 23:06:36 +0100	[thread overview]
Message-ID: <1eb864d2-3693-533f-0136-b6e22d3e5ae6@emagii.com> (raw)
In-Reply-To: <20230314220114.1117782-1-binutils@emagii.com>

There are no NEWS, ld.texi or testsuite for these patches yet
since they are just RFCs at the moment.

Need to get the copyright issue sorted out.

I finally got reply from FSF on Copyrights, but they think it could take
some time to process.

Best Regards
Ulf Samuelsson

On 2023-03-14 23:01, Ulf Samuelsson via Binutils wrote:
> Patchset 1
>
> Introduce the CHIP command for non-MRI script files.
>
> The motivation is that you want to simplify supporting microcontrollers.
> You want include files that define the addresses for all peripherals
> and the memory/bank organisation.
>
> CHIP "<chip>" will add directories to the include directory list
> and will then include the "<chip>.inc" file.
>
> chip "<chip>" will add
> * "$PROJ_DIR"
> * "$LD_USER_DIR/<chip>"
> * "$LD_VENDOR_DIR/<chip>"
> to the search list for script files.
>
> The search order will be:
>
> "<Current directory>"
> "$PROJ_DIR"
> "$LD_USER_DIR/<chip>"
> "$LD_VENDOR_DIR/<chip>"
>
> This allows the vendor to supply a directory tree (LD_VENDOR_DIR).
> with a subdirectory for each chip.
>
> The subdirectory contains the "<chip>.inc" file which
> can have the flash sectors using the BANK command
> (patch posted to the link) as well as symbols
> for all the peripherals for the chip.
>
> Obviously, the vendor can place other files there as well.
>
> chip "at91sam7s64"
>
> would result in the linker including the file
> $LD_VENDOR_DIR/at91sam7s64/at91sam7s64.inc
>
> Since the vendor might be late with supplying include files
> for a chip, the user can create a similar directory in LD_USER_DIR.
>
> chip "at91sam7s64"
>
> This would result in the linker including the file
> $LD_USER_DIR/atmel/at91sam7s64/at91sam7s64.inc
> since LD_USER_DIR is before LD_VENDOR_DIR in the search order.
>
> If the user wants to simply put the file in their project
> they can rely on the search order, or put the file in $PROJ_DIR
>
> chip "at91sam7s64";
>
> This would result in the linker including the file
> $PROJ_DIR/at91sam7s64.inc
>
> =================================
>
> I am considering a further extension:
>
> chip "at91sam7s64", "atmel";
>
> This would result in the linker including the file
> $LD_VENDOR_DIR/atmel/at91sam7s64/at91sam7s64.inc
>
> [PATCH v1 1/3] CHIP: ldlex.l
> [PATCH v1 2/3] CHIP: ldgram.y
> [PATCH v1 3/3] CHIP: language additions
>

  parent reply	other threads:[~2023-03-14 22:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 22:01 binutils
2023-03-14 22:01 ` [PATCH v1 1/3] CHIP: ldlex.l binutils
2023-03-14 22:01 ` [PATCH v1 2/3] CHIP: ldgram.y binutils
2023-03-14 22:01 ` [PATCH v1 3/3] CHIP: language additions binutils
2023-03-14 22:06 ` Ulf Samuelsson [this message]
2023-03-15 16:27 ` [PATCH v1 0/3 CHIP: Support vendor script libraries Michael Matz
2023-03-15 20:03   ` Ulf Samuelsson
2023-03-16  8:23     ` Jan Beulich
2023-03-16 10:25       ` Ulf Samuelsson
2023-03-16 15:05     ` Michael Matz
2023-03-16 15:57       ` Ulf Samuelsson

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=1eb864d2-3693-533f-0136-b6e22d3e5ae6@emagii.com \
    --to=binutils@emagii.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).