> >   In fact, in most cases, I'd like to make the .dts file part of
quoted text
> > the bitstream and not compiled into the kernel.
> 
> Well, I've just run out of BRAM on a V5LX50T design so please don't
ask
quoted text
> for more of it to store a DTC! :)  Or do you mean to piggyback on the
> tail of the configuration stream and read with some kind of JTAG user
> code?

That's a possibility.  More likely, it can get stuffed in the low BRAM
and ripped out during boot time.  I've got the same trick working on
ppc, using the BRAM at the reset vector.  

quoted text
> > Although powerpc has a bit more boot-time complexity than the
microblaze
quoted text
> > does currently, I think it makes alot of sense to have some
consistency
quoted text
> > here, and there is already a pattern to follow here which nicely
> > orthogonalizes multiple .dts files for the same platform code.
> 
> arch/powerpc/boot is building a bootloader, so maybe that's why .dts
> files belong there.  The bootloader is really the only thing that
cares
quoted text
> about them as objects.  Once the kernel starts, it's just
dereferencing
quoted text
> a pointer that happens to point to a datastructure it understands (or
> copying it as a blob before doing same).
> 
> In fact, you could mount an argument that .dts files don't belong
> anywhere near the MicroBlaze kernel, since our build process never
> actually touches them.

Well, that was part of my argument that they shouldn't be part of the
platform code, but I guess I wasn't clear enough... :)

Steve



--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/