* Ian Campbell [2016-08-04 10:03]:
> Seems fine by me. It does assume that DTB filenames are unique even
> when the directory hierarchy. That seems fairly likely to be true,
> but it may not be guaranteed I guess.
True, that's an assumption I made but I think it's pretty safe
On Sun, 2016-07-31 at 13:11 -0700, Martin Michlmayr wrote:
> > * Ian Campbell [2016-07-31 10:20]:
> >
> > I've attached the two patches I had sitting in my branch here, they
> > look sensible but I honestly can't remember what state they are in.
> >
> > AFAICT the main
* Ian Campbell [2016-07-31 10:20]:
> I've attached the two patches I had sitting in my branch here, they
> look sensible but I honestly can't remember what state they are in.
>
> AFAICT the main difference is that they preserve the directory layout
> rather than collapsing it.
On Sat, 2016-07-30 at 16:52 -0700, Martin Michlmayr wrote:
> DTBs on arm64 are stored as vendor/dtb rather than everything in one
> directory.
I looked at this a while back but it seems I never completed it, or at
least never pushed it :-(.
I've attached the two patches I had sitting in my
* Vagrant Cascadian [2016-07-30 17:23]:
> Thanks for the patch! Looks good and simple to me.
>
> I presume the database entries for platforms that need it would then
> include the vendor like this:
>
> DTB-Id: VENDOR/PLATFORM.dtb
Correct.
--
Martin Michlmayr
On 2016-07-30, Martin Michlmayr wrote:
> DTBs on arm64 are stored as vendor/dtb rather than everything in one
> directory. flash-kernel doesn't handle this at the moment. I see two
> options:
>
> 1) Strip the vendor dir away and install the dtb as
> /boot/dtbs/$kvers/dtb
>
> 2) Keep the
DTBs on arm64 are stored as vendor/dtb rather than everything in one
directory. flash-kernel doesn't handle this at the moment. I see two
options:
1) Strip the vendor dir away and install the dtb as
/boot/dtbs/$kvers/dtb
2) Keep the directory and install as /boot/dtbs/$kvers/vendor/dtb
In
7 matches
Mail list logo