On Sun, 2015-06-21 at 08:31 -0700, Vagrant Cascadian wrote:
> On 2015-06-14, Ian Campbell wrote:
> > Attached is a patch to enable support for the Jetson Tegra K1 board via a 
> > new
> > u-boot-tegra package. It is based on the experimental-2015.07 branch of 
> > git. I
> > can push it myself if you prefer but I thought I'd best have it reviewed 
> > first.
> 
> Looks fine to me. Feel free to commit it!

Thanks, will do (maybe not until the weekend though).

> One question this brings up, though: According to wikipedia, there is
> also a 64-bit variant; would that use a different u-boot?

I _think_ (and I'm only 90% sure) that the 64-bit SoC is called the
Tegra X1, rather than K1. I'm not aware yet of a 64-bit dev board with
this SoC though I suppose there will be something eventually.

> All the u-boot packages are marked "multi-arch: same", but if there's
> the possibility of both an armhf and amd64 u-boot-tegra package
> containing different builds, maybe we'll need to reconsider how to
> handle multi-arch with u-boot packaging...

Hrm, so u-boot-tegra:armhf and u-boot-tegra:arm64 cannot be installed at
the same time? even if the files which they contain do not overlap?

They shouldn't contain overlapping files[0] which I thought was enough
to allow multiple arches to be installed.

[0] or at least I think it's unlikely any 64-bit board will be called
precisely "jetson-tk1" (-tx1, maybe...)

> > I'm not entirely happy with the requirement (documented in the README) to 
> > use
> > L4T to do the flashing but I've not yet worked out a fully working 
> > alternative
> > (I think something must be possible using some combination of tegracrm and
> > cbotimage both of which are in Debian, but I've not figured out the exact 
> > steps
> > yet).
> 
> You could perhaps include a TODO item in the README (or a separate TODO
> file); that might stir someone else to submit improved docs...

A good idea, thanks.

Ian.


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to