From: Alexander Dahl <ada@thorsis.com>
To: Michael Olbrich <m.olbrich@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC 3/4] libptxdist: add a function to find unreferenced source directories
Date: Mon, 09 Sep 2019 09:46:30 +0200 [thread overview]
Message-ID: <29589436.F181zHvTYY@ada> (raw)
In-Reply-To: <20190909062300.w6jbjiywrl5oqrva@pengutronix.de>
Hei hei,
Am Montag, 9. September 2019, 08:23:00 CEST schrieb Michael Olbrich:
> On Wed, Sep 04, 2019 at 03:16:51PM +0200, Alexander Dahl wrote:
> > Am Mittwoch, 4. September 2019, 15:05:04 CEST schrieb Michael Olbrich:
> > > On Fri, Aug 23, 2019 at 11:01:58AM +0200, Alexander Dahl wrote:
> > > > FWIW, we are still using different versions of at91bootstrap in
> > > > different
> > > > BSPs. The legacy version (at91bootstrap) has patches in the directory
> > > > 'patches/Bootstrap-v1.16' and the current version (at91bootstrap2) has
> > > > them in 'patches/at91bootstrap-3.8.13'.
> > > >
> > > > If one or the other package needs fixes, let me know.
> > >
> > > PTXdist upstream has patches for 'at91bootstrap'. Do you use those, or
> > > do
> > > you have your own patch stack in your BSP?
> > >
> > > I'd like to remove the patches from PTXdist. It's the only packages that
> > > has a configurable version and patches for one specific version
> > > upstream.
> >
> > We have our own patches anyway.
> >
> > And even if not, it would also be no problem to add them to our BSP, if
> > ptxdist won't ship those anymore.
>
> Hmm, so I noticed that I actually run build tests for this. And I'd
> probably loose those if I drop the patches...
>
> So another Idea: From what I understand, Upstream for this is dead, so
> there will be no new version, right? Can I assume, that nowadays only
> version 1.16 is used?
This is at91bootstrap version 1, from my point of view upstream focus is now
on version 3 only (the ptxdist package is called 'at91bootstrap2'). You choose
one or the other depending on your SoC/board, AFAIK there are only very few
boards supported by both, if any.
And: you can avoid at91bootstrap at all and use the SPL variant of U-Boot or
barebox instead for this stage of the bootloaders. (We never tried that.)
> In that case I could just remove the version options and keep the patches.
> That way all my scripts are happy and it's still covered in my build tests.
>
> Alex, would that make sense to you?
If you just want to pin the version to v1.16, I'm fine with that.
> Ladis, you submitted the last patch for this. Is this still relevant for
> you? What do you think?
>
> Michael
Greets
Alex
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-09-09 7:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 10:42 [ptxdist] [RFC 1/4] patches/HEADER: remove apparently outdated and unreferenced file Roland Hieber
2019-08-22 10:42 ` [ptxdist] [RFC 2/4] Makefile.in: sort environment tools alphabetically Roland Hieber
2019-08-22 10:42 ` [ptxdist] [RFC 3/4] libptxdist: add a function to find unreferenced source directories Roland Hieber
2019-08-22 10:53 ` Roland Hieber
2019-08-22 12:43 ` Uwe Kleine-König
2019-08-22 15:38 ` Michael Olbrich
2019-08-23 8:33 ` Roland Hieber
2019-08-23 9:01 ` Alexander Dahl
2019-09-04 13:05 ` Michael Olbrich
2019-09-04 13:16 ` Alexander Dahl
2019-09-09 6:23 ` Michael Olbrich
2019-09-09 7:46 ` Alexander Dahl [this message]
2019-09-09 20:33 ` Ladislav Michl
2019-09-10 8:13 ` Michael Olbrich
2019-08-22 10:42 ` [ptxdist] [RFC 4/4] ptxdist: add a 'lint' subcommand Roland Hieber
2019-08-22 11:44 ` [ptxdist] [RFC 1/4] patches/HEADER: remove apparently outdated and unreferenced file Robert Schwebel
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=29589436.F181zHvTYY@ada \
--to=ada@thorsis.com \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox