| Message ID | 1373659247-1775-4-git-send-email-swarren@wwwdotorg.org |
|---|---|
| State | New |
| Headers | show |
On 07/12/2013 02:00 PM, Stephen Warren wrote: > From: Stephen Warren <swarren@nvidia.com> > > In order to support Tegra in d-i, we need to package kernel modules for > both Tegra SoC modules and various devices used on Tegra board, and also > build and package all Tegra-related device tree files. > > For now, we only include support for Tegra20 boards, and not Tegra30/114 > boards, since the kernel only has support for USB on Tegra20 so far, and > USB is required for any networking on Tegra, so this limits where the d-i > netinstall will actually be useful. BTW, I found that in this patch, I forgot to add i2c-tegra.ko. Once this series is reviewed I can repost with that fix, or send another patch; whichever you want.
On 07/18/2013 10:14 AM, Stephen Warren wrote: > On 07/12/2013 02:00 PM, Stephen Warren wrote: >> From: Stephen Warren <swarren@nvidia.com> >> >> In order to support Tegra in d-i, we need to package kernel modules for >> both Tegra SoC modules and various devices used on Tegra board, and also >> build and package all Tegra-related device tree files. >> >> For now, we only include support for Tegra20 boards, and not Tegra30/114 >> boards, since the kernel only has support for USB on Tegra20 so far, and >> USB is required for any networking on Tegra, so this limits where the d-i >> netinstall will actually be useful. > > BTW, I found that in this patch, I forgot to add i2c-tegra.ko. Once this > series is reviewed I can repost with that fix, or send another patch; > whichever you want. > We're past review. Andy has already applied it.
Tim Gardner wrote at Thursday, July 18, 2013 11:48 AM: > On 07/18/2013 10:14 AM, Stephen Warren wrote: > > On 07/12/2013 02:00 PM, Stephen Warren wrote: > >> From: Stephen Warren <swarren@nvidia.com> > >> > >> In order to support Tegra in d-i, we need to package kernel modules for > >> both Tegra SoC modules and various devices used on Tegra board, and also > >> build and package all Tegra-related device tree files. > >> > >> For now, we only include support for Tegra20 boards, and not Tegra30/114 > >> boards, since the kernel only has support for USB on Tegra20 so far, and > >> USB is required for any networking on Tegra, so this limits where the d-i > >> netinstall will actually be useful. > > > > BTW, I found that in this patch, I forgot to add i2c-tegra.ko. Once this > > series is reviewed I can repost with that fix, or send another patch; > > whichever you want. > > > > We're past review. Andy has already applied it. Oh, so he has. Thanks! When Andy said he was looking at the patches, I didn't realize that meant he would definitely apply them.
On 07/18/2013 11:55 AM, Stephen Warren wrote: > Tim Gardner wrote at Thursday, July 18, 2013 11:48 AM: >> On 07/18/2013 10:14 AM, Stephen Warren wrote: >>> On 07/12/2013 02:00 PM, Stephen Warren wrote: >>>> From: Stephen Warren <swarren@nvidia.com> >>>> >>>> In order to support Tegra in d-i, we need to package kernel modules for >>>> both Tegra SoC modules and various devices used on Tegra board, and also >>>> build and package all Tegra-related device tree files. >>>> >>>> For now, we only include support for Tegra20 boards, and not Tegra30/114 >>>> boards, since the kernel only has support for USB on Tegra20 so far, and >>>> USB is required for any networking on Tegra, so this limits where the d-i >>>> netinstall will actually be useful. >>> >>> BTW, I found that in this patch, I forgot to add i2c-tegra.ko. Once this >>> series is reviewed I can repost with that fix, or send another patch; >>> whichever you want. >>> >> >> We're past review. Andy has already applied it. > > Oh, so he has. Thanks! When Andy said he was looking at the patches, I didn't > realize that meant he would definitely apply them. > Huh. I prompted Andy to respond yesterday that he _had_ applied your patches. I swear I saw his response, but its not in the list serv archive. Anyways, I guess you can consider yourself notified :) rtg
diff --git a/debian.master/d-i/firmware/kernel-image b/debian.master/d-i/firmware/kernel-image index 1a8423a..4949089 100644 --- a/debian.master/d-i/firmware/kernel-image +++ b/debian.master/d-i/firmware/kernel-image @@ -3,3 +3,9 @@ device-tree/imx6q-sabrelite.dtb device-tree/omap3-beagle-xm.dtb device-tree/omap4-panda.dtb device-tree/omap4-panda-es.dtb +device-tree/tegra20-harmony.dtb +device-tree/tegra20-paz00.dtb +device-tree/tegra20-seaboard.dtb +device-tree/tegra20-trimslice.dtb +device-tree/tegra20-ventana.dtb +device-tree/tegra20-whistler.dtb diff --git a/debian.master/d-i/modules/block-modules b/debian.master/d-i/modules/block-modules index 97d5cb3..546c900 100644 --- a/debian.master/d-i/modules/block-modules +++ b/debian.master/d-i/modules/block-modules @@ -25,6 +25,7 @@ pd ? pf ? pg ? pt ? +sdhci-tegra ? sx8 ? umem ? virtio_blk ? diff --git a/debian.master/d-i/modules/kernel-image b/debian.master/d-i/modules/kernel-image new file mode 100644 index 0000000..e9deb50 --- /dev/null +++ b/debian.master/d-i/modules/kernel-image @@ -0,0 +1,23 @@ +gpio-pca953x ? +gpio-regulator ? +i2c-mux ? +i2c-mux-pinctrl ? +max8907 ? +max8907-regulator ? +nvec ? +nvec_kbd ? +nvec_paz00 ? +nvec_power ? +nvec_ps2 ? +palmas-regulator ? +rtc-em3027 ? +rtc-max8907 ? +rtc-palmas ? +rtc-tps6586x ? +rtc-tps65910 ? +tps51632-regulator ? +tps62360-regulator ? +tps65090-charger ? +tps65090-regulator ? +tps6586x-regulator ? +tps65910-regulator ? diff --git a/debian.master/rules.d/armhf.mk b/debian.master/rules.d/armhf.mk index 8aca879..181240b 100644 --- a/debian.master/rules.d/armhf.mk +++ b/debian.master/rules.d/armhf.mk @@ -19,3 +19,9 @@ dtb_files_generic += imx6q-sabrelite.dtb dtb_files_generic += omap3-beagle-xm.dtb dtb_files_generic += omap4-panda.dtb dtb_files_generic += omap4-panda-es.dtb +dtb_files_generic += tegra20-harmony.dtb +dtb_files_generic += tegra20-paz00.dtb +dtb_files_generic += tegra20-seaboard.dtb +dtb_files_generic += tegra20-trimslice.dtb +dtb_files_generic += tegra20-ventana.dtb +dtb_files_generic += tegra20-whistler.dtb