On Wed, Sep 10, 2014 at 09:36:32AM -0700, Olof Johansson wrote: > On Wed, Sep 10, 2014 at 7:31 AM, Mark Brown <broonie@xxxxxxxxxx> wrote: > > As well as the regulators we'll also need to fix the clocks. If we're > > going to start adding these fixups perhaps we want to consider having a > > wrapper stage that deals with rewriting DTs prior to trying to use them? > > I'm not sure if it makes much difference but there's overlap with other > > tools like the ATAGs conversion wrapper and building separately would > > let the fixup code run early without directly going into the early init > > code (which seems a bit scary). > I'm strongly against doing this outside of the kernel, since they're > closely tied together today. We've always had the quirk tables for > devices in the kernel, and we used to do this a long time ago on > powerpc as well (we did it before we built the flat DT out of the OF > equivalent there, most of the time). Indeed - sorry, the above wasn't adequately clear. I think that we should build this separately but keep it part of the kernel source. The split I was thinking of was purely technical. > > As far as I can tell the problem here is coming from the decision to > > have simplefb use resources without knowing about them - can we agree > > that this is a bad idea? > As already argued, there are good reasons to sometimes allow this, as > long as it can be expected that it's something that's just used during > early boot. For example, having DEBUG_LL output on a pre-mapped > framebuffer could be really useful. Once DRM comes up, it'll tear down > the existing one. The problem here seems to be that that just during early boot assumption isn't playing out so well...
Attachment:
signature.asc
Description: Digital signature
