mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Kees-Jan Dijkzeul <k.j.dijkzeul@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Is anyone still using grub legacy?
Date: Mon, 6 Feb 2023 18:51:49 +0100	[thread overview]
Message-ID: <CAP_6oj64+VeqCBk-+P+ADiJNW0gY-fOXkVrd6jByZ52JT_cp9g@mail.gmail.com> (raw)
In-Reply-To: <CAP_6oj6msMKUeuacSR_D5uSOwEnRLV1ptS=c8RxhwbseF5f=_Q@mail.gmail.com>

Hi,

Many years ago, my customer created an embedded distribution for their
X86 product using ptxdist with grub legacy. With recent versions of
ptxdist and toolchains, they are increasingly struggling to keep
things working, and I am now trying to untangle the resulting mess.

When I started, I assumed that grub legacy as build by ptxdist would
actually be working. But as time goes by, I'm beginning to have
doubts.

Hence this question to check my sanity: Are there ptxdist users that
use grub legacy? Is it working? Do you need any additional patches,
and if so which ones?

Thanks!

Kees-Jan



           reply	other threads:[~2023-02-06 17:52 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAP_6oj6msMKUeuacSR_D5uSOwEnRLV1ptS=c8RxhwbseF5f=_Q@mail.gmail.com>]

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=CAP_6oj64+VeqCBk-+P+ADiJNW0gY-fOXkVrd6jByZ52JT_cp9g@mail.gmail.com \
    --to=k.j.dijkzeul@gmail.com \
    --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