DistroKit Mailinglist
 help / color / mirror / Atom feed
From: Roland Hieber <r.hieber@pengutronix.de>
To: Robert Schwebel <r.schwebel@pengutronix.de>
Cc: Michael Olbrich <m.olbrich@pengutronix.de>, distrokit@pengutronix.de
Subject: Re: [DistroKit] [PATCH 0/3] platform-rpi: various cleanups
Date: Wed, 31 Oct 2018 23:37:38 +0100	[thread overview]
Message-ID: <20181031223738.emsmprmcggivzryh@pengutronix.de> (raw)
In-Reply-To: <20181026132916.gxx5t77jtv4nr2h2@pengutronix.de>

On Fri, Oct 26, 2018 at 03:29:16PM +0200, Robert Schwebel wrote:
> On Fri, Oct 26, 2018 at 02:15:52PM +0200, Michael Olbrich wrote:
> > I built the rpi platform to check that my layer change works correctly and
> > I noticed some other issues. These are just some minor fixes and cleanups.
> > 
> > I also noticed that the kernel config is quite different from the v7a
> > config. Some of that seems to be pretty arbitrary and suboptimal. E.g. no
> > optimized ARM crypto implementations, no idle handler and things like that.
> > Is there a reason for this?
> 
> I don't think so, but I havn't cared much about the RPi. Roland might
> have more insights, but he is currently on holiday.

The basic state is "rpi boots a kernel", nothing more. Due to lack of
use in RPI 1 I haven't gotten around to having a better look and
cleaning up the config yet. But I wonder now that ptxdist has layer
support - could that already be used for building up a kernel config
from a platform-independent part that stays the same as a baseline for
all platforms and a platform-dependent part which only switches on the
respective platform support, drivers etc?

 - Roland

-- 
Roland Hieber                     | r.hieber@pengutronix.de     |
Pengutronix e.K.                  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917-5555 |

_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de

  reply	other threads:[~2018-10-31 22:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-26 12:15 Michael Olbrich
2018-10-26 12:15 ` [DistroKit] [PATCH 1/3] platform-rpi: image-boot-vfat: add missing dependency Michael Olbrich
2018-10-26 12:15 ` [DistroKit] [PATCH 2/3] platform-rpi: platformconfig: building the kernel requires openssl Michael Olbrich
2018-10-26 12:15 ` [DistroKit] [PATCH 3/3] platform-rpi: platformconfig: some cleanup Michael Olbrich
2018-10-26 13:29 ` [DistroKit] [PATCH 0/3] platform-rpi: various cleanups Robert Schwebel
2018-10-31 22:37   ` Roland Hieber [this message]
2018-11-01  9:42     ` Michael Olbrich
2018-11-01  9:55       ` 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=20181031223738.emsmprmcggivzryh@pengutronix.de \
    --to=r.hieber@pengutronix.de \
    --cc=distrokit@pengutronix.de \
    --cc=m.olbrich@pengutronix.de \
    --cc=r.schwebel@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