RE: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
> -Original Message- > From: Kevin Hilman [mailto:khil...@linaro.org] > Sent: Thursday, June 13, 2013 4:09 AM > To: Hiremath, Vaibhav > Cc: Vutla, Lokesh; Paul Walmsley; Shilimkar, Santosh; t...@atomide.com; > linux-arm-ker...@lists.infradead.org; linux-omap@vger.kernel.org; R, > Sricharan; Nayak, Rajendra > Subject: Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr > info clean up > > Hi Vaibhav, > > "Hiremath, Vaibhav" writes: > > [...] > > > Paul/Kevin/Santosh, > > > > AM335x is booting up from Mainline, starting from v3.7, that’s where > HWMOD data got merged to > > Mainline. > > > > We have discussed on this in the past as well, let me explain the > issue here in detail > > again for everybody - > > Thanks for the detail. > > In my case, after more debug, it appears that where I was putting the > DTB in memory from u-boot was not working. Using the addresses you > used gets things working again. Thanks. > > u-boot mainline (v2013.04) for BeagleBone has defaults that don't work > appear together: > > U-Boot# printenv loadaddr > loadaddr=0x8020 > U-Boot# printenv fdtaddr > fdtaddr=0x80F8 > I tried above address and it is booting up for me, below is the log for your reference - Boot LOG: = U-Boot SPL 2013.04-00274-ga71d45d (Jun 12 2013 - 10:54:45) musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 OMAP SD/MMC: 0 reading u-boot.img reading u-boot.img U-Boot 2013.04-00274-ga71d45d (Jun 12 2013 - 10:54:45) I2C: ready DRAM: 512 MiB WARNING: Caches not enabled NAND: No NAND device found!!! 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Peripheral mode controller at 47401000 using PIO, IRQ 0 musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn) musb-hdrc: MHDRC RTL version 2.0 musb-hdrc: setup fifo_mode 4 musb-hdrc: 28/31 max ep, 16384/16384 memory USB Host mode controller at 47401800 using PIO, IRQ 0 Net:not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 U-Boot# U-Boot# U-Boot# U-Boot# U-Boot# U-Boot# U-Boot# mmc rescan U-Boot# fatload mmc 0 0x80F8 am335x-bone.dtb reading am335x-bone.dtb 8865 bytes read in 6 ms (1.4 MiB/s) U-Boot# fatload mmc 0 0x8020 uImage reading uImage 4044224 bytes read in 464 ms (8.3 MiB/s) U-Boot# fatload mmc 0 8200 ramdisk-pm.gz reading ramdisk-pm.gz 2022580 bytes read in 235 ms (8.2 MiB/s) U-Boot# setenv bootargs console=ttyO0,115200n8 mem=256M root=/dev/ram rw initrd=0x8200,32MB ramdisk_size=65536 earlyprintk=serial omap_wdt.nowayout=60 U-Boot# bootm 0x8020 - 0x80F8 ## Booting kernel from Legacy Image at 8020 ... Image Name: Linux-3.10.0-rc5-00054-g75da4e1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:4044160 Bytes = 3.9 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK ## Flattened Device Tree blob at 80f8 Booting using the fdt blob at 0x80f8 Loading Kernel Image ... OK OK Using Device Tree in place at 80f8, end 80f852a0 Starting kernel ... [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 3.10.0-rc5-00054-g75da4e1 (a0393758@psplinux064) (gcc version 4.5.3 20110311 (prerelease) (GCC) ) #1 SMP Wed Jun 12 10:51:03 IST 2013 [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x BeagleBone [0.00] cma: CMA: reserved 16 MiB at 8e80 [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] CPU: All CPU(s) started in SVC mode. [0.00] AM335X ES2.0 (neon ) [0.00] PERCPU: Embedded 9 pages/cpu @c0f83000 s13632 r8192 d15040 u36864 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 64768 [0.00] Kernel command line: console=ttyO0,115200n8 mem=256M root=/dev/ram rw initrd=0x8200,32MB ramdisk_size=65536 earlyprintk=serial omap_wdt.nowayout=60 [0.00] Booting kernel: `60' invalid
Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
Hi Vaibhav, "Hiremath, Vaibhav" writes: [...] > Paul/Kevin/Santosh, > > AM335x is booting up from Mainline, starting from v3.7, that’s where HWMOD > data got merged to > Mainline. > > We have discussed on this in the past as well, let me explain the issue here > in detail > again for everybody - Thanks for the detail. In my case, after more debug, it appears that where I was putting the DTB in memory from u-boot was not working. Using the addresses you used gets things working again. Thanks. u-boot mainline (v2013.04) for BeagleBone has defaults that don't work appear together: U-Boot# printenv loadaddr loadaddr=0x8020 U-Boot# printenv fdtaddr fdtaddr=0x80F8 Changing fdtaddr around got things working again. It's probably a good idea to change the u-boot defaults to values that work, since that's a likely starting point for people. I'm now back to mainline booting well on both my original BeagleBone and my BeagleBone black. Thanks, Kevin > In case of Am335x we have only two possible options, as AM335x only boots up > With DTB (Tested in BBB) - > > 1. Mainline u-boot + mainline Kernel: > = > > 1.a. Appended DTB method > > > Here you __must__ enabled below config options in order to get kernel booting, > > CONFIG_ARM_APPENDED_DTB=y > CONFIG_ARM_ATAG_DTB_COMPAT=y > CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y > > And, I have used below command to append DTB to kernel image > > # cat arch/arm/boot/zImage arch/arm/boot/dts/am335x-bone.dtb > > zImage-append && mkimage -A arm -O linux -T kernel -C none -a > 0x80008000 -e 0x80008000 -n "Linux" -d zImage-append uImage-append > > > I have attached complete log here with this mail for reference > http://pastebin.com/82duFh78 > > > 1.b. Discrete DTB and uImage method: > > > Here you don’t need to enable any extra config options. Plain > omap2plus_defconfig > Should work without any issues. > > I have attached complete log here with this mail for reference > http://pastebin.com/Nqr0PiwW > > > 2. Older U-Boot (without DTB) + Mainline Kernel: > > > This is same as #OPTION-1.a above. > > > Thanks, > Vaibhav -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
> -Original Message- > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > ow...@vger.kernel.org] On Behalf Of Hiremath, Vaibhav > Sent: Wednesday, June 12, 2013 11:34 AM > To: Kevin Hilman; Paul Walmsley > Cc: Shilimkar, Santosh; t...@atomide.com; linux-arm- > ker...@lists.infradead.org; linux-omap@vger.kernel.org; R, Sricharan > Subject: RE: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr > info clean up > > > > -Original Message- > > From: Kevin Hilman [mailto:khil...@linaro.org] > > Sent: Friday, June 07, 2013 3:57 AM > > To: Paul Walmsley > > Cc: Shilimkar, Santosh; t...@atomide.com; linux-arm- > > ker...@lists.infradead.org; linux-omap@vger.kernel.org; Hiremath, > > Vaibhav; R, Sricharan > > Subject: Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr > > info clean up > > > > Paul Walmsley writes: > > > > > On Wed, 29 May 2013, Santosh Shilimkar wrote: > > > > > >> From: Vaibhav Hiremath > > >> > > >> AM33XX only supports DT boot mode and with addition of > > >> extracting module resources like, irq, dma and address space > > >> from DT block, so now we can remove duplicate information from > > >> hwmod data file. > > > > > > OK, guess I'll take your word for it that it all works. The > > > BeagleBone-white with appended DTB hasn't booted here since v3.7. > > > And the BeagleBone-black with discrete DTB doesn't boot at all with > > > current mainline, only with the TI vendor kernel & DTB... > > > > Anyone care to shed light on what's missing for BeagleBone boot with > > mainline currently? > > > > I've also not been able to boot a mainline kernel on the BeagleBone > for > > some time. > > > > Sorry for delayed response, as I was on vacation for almost for a week. > > I have just responded to this thread on complete analysis of the issue. > > http://www.mail-archive.com/linux-omap@vger.kernel.org/msg90309.html > I have also pushed the branch to github, https://github.com/hvaibhav/am335x-linux.git linus-master OR https://github.com/hvaibhav/am335x-linux/tree/linus-master NOTE: Tested on BeagleBone-Black platform. Thanks, Vaibhav -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
> -Original Message- > From: Kevin Hilman [mailto:khil...@linaro.org] > Sent: Friday, June 07, 2013 3:57 AM > To: Paul Walmsley > Cc: Shilimkar, Santosh; t...@atomide.com; linux-arm- > ker...@lists.infradead.org; linux-omap@vger.kernel.org; Hiremath, > Vaibhav; R, Sricharan > Subject: Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr > info clean up > > Paul Walmsley writes: > > > On Wed, 29 May 2013, Santosh Shilimkar wrote: > > > >> From: Vaibhav Hiremath > >> > >> AM33XX only supports DT boot mode and with addition of > >> extracting module resources like, irq, dma and address space > >> from DT block, so now we can remove duplicate information from > >> hwmod data file. > > > > OK, guess I'll take your word for it that it all works. The > > BeagleBone-white with appended DTB hasn't booted here since v3.7. > > And the BeagleBone-black with discrete DTB doesn't boot at all with > > current mainline, only with the TI vendor kernel & DTB... > > Anyone care to shed light on what's missing for BeagleBone boot with > mainline currently? > > I've also not been able to boot a mainline kernel on the BeagleBone for > some time. > Sorry for delayed response, as I was on vacation for almost for a week. I have just responded to this thread on complete analysis of the issue. http://www.mail-archive.com/linux-omap@vger.kernel.org/msg90309.html Thanks, Vaibhav -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
> -Original Message- > From: Vutla, Lokesh > Sent: Tuesday, June 11, 2013 9:45 AM > To: Kevin Hilman > Cc: Paul Walmsley; Shilimkar, Santosh; t...@atomide.com; linux-arm- > ker...@lists.infradead.org; linux-omap@vger.kernel.org; Hiremath, > Vaibhav; R, Sricharan; Nayak, Rajendra > Subject: Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr > info clean up > > Hi Kevin, > On Monday 10 June 2013 10:33 PM, Kevin Hilman wrote: > > Hi Lokesh, > > > > Lokesh Vutla writes: > > > >> Hi Kevin, > >> > >> On Friday 07 June 2013 03:57 AM, Kevin Hilman wrote: > >>> Paul Walmsley writes: > >>> > >>>> On Wed, 29 May 2013, Santosh Shilimkar wrote: > >>>> > >>>>> From: Vaibhav Hiremath > >>>>> > >>>>> AM33XX only supports DT boot mode and with addition of > >>>>> extracting module resources like, irq, dma and address space > >>>>> from DT block, so now we can remove duplicate information from > >>>>> hwmod data file. > >>>> > >>>> OK, guess I'll take your word for it that it all works. The > >>>> BeagleBone-white with appended DTB hasn't booted here since v3.7. > >>>> And the BeagleBone-black with discrete DTB doesn't boot at all > with > >>>> current mainline, only with the TI vendor kernel & DTB... > >>> > >>> Anyone care to shed light on what's missing for BeagleBone boot > with > >>> mainline currently? > >> I have tested BeagleBone boot with today's mainline bootloader and > >> kernel. It boots perfectly fine. > > > > Can you post git trees + branch names (and/or commit IDs) and also > > kernel config please? > Following are the details: > U-Boot: > url: git://git.denx.de/u-boot.git > branch : master > config: am335x_evm > Top commit: "842033e pci: introduce CONFIG_PCI_INDIRECT_BRIDGE > option" > > Kernel: > url: > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux- > 2.6.git > branch: master > config: omap2plus_defocnfig > dtb file: am335x-bone.dtb > Top commit: "317ddd2 Linux 3.10-rc5" (On top of this I have a local > patch for appending dtb) > You can find the logs here: http://pastebin.com/vcBr0UhM > Paul/Kevin/Santosh, AM335x is booting up from Mainline, starting from v3.7, that’s where HWMOD data got merged to Mainline. We have discussed on this in the past as well, let me explain the issue here in detail again for everybody - In case of Am335x we have only two possible options, as AM335x only boots up With DTB (Tested in BBB) - 1. Mainline u-boot + mainline Kernel: = 1.a. Appended DTB method Here you __must__ enabled below config options in order to get kernel booting, CONFIG_ARM_APPENDED_DTB=y CONFIG_ARM_ATAG_DTB_COMPAT=y CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y And, I have used below command to append DTB to kernel image # cat arch/arm/boot/zImage arch/arm/boot/dts/am335x-bone.dtb > zImage-append && mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n "Linux" -d zImage-append uImage-append I have attached complete log here with this mail for reference http://pastebin.com/82duFh78 1.b. Discrete DTB and uImage method: Here you don’t need to enable any extra config options. Plain omap2plus_defconfig Should work without any issues. I have attached complete log here with this mail for reference http://pastebin.com/Nqr0PiwW 2. Older U-Boot (without DTB) + Mainline Kernel: This is same as #OPTION-1.a above. Thanks, Vaibhav -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
Hi Kevin, On Monday 10 June 2013 10:33 PM, Kevin Hilman wrote: Hi Lokesh, Lokesh Vutla writes: Hi Kevin, On Friday 07 June 2013 03:57 AM, Kevin Hilman wrote: Paul Walmsley writes: On Wed, 29 May 2013, Santosh Shilimkar wrote: From: Vaibhav Hiremath AM33XX only supports DT boot mode and with addition of extracting module resources like, irq, dma and address space from DT block, so now we can remove duplicate information from hwmod data file. OK, guess I'll take your word for it that it all works. The BeagleBone-white with appended DTB hasn't booted here since v3.7. And the BeagleBone-black with discrete DTB doesn't boot at all with current mainline, only with the TI vendor kernel & DTB... Anyone care to shed light on what's missing for BeagleBone boot with mainline currently? I have tested BeagleBone boot with today's mainline bootloader and kernel. It boots perfectly fine. Can you post git trees + branch names (and/or commit IDs) and also kernel config please? Following are the details: U-Boot: url:git://git.denx.de/u-boot.git branch :master config: am335x_evm Top commit: "842033e pci: introduce CONFIG_PCI_INDIRECT_BRIDGE option" Kernel: url: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git branch: master config: omap2plus_defocnfig dtb file: am335x-bone.dtb Top commit: "317ddd2 Linux 3.10-rc5" (On top of this I have a local patch for appending dtb) You can find the logs here: http://pastebin.com/vcBr0UhM Thanks and regards, Lokesh Thanks, Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
Hi Lokesh, Lokesh Vutla writes: > Hi Kevin, > > On Friday 07 June 2013 03:57 AM, Kevin Hilman wrote: >> Paul Walmsley writes: >> >>> On Wed, 29 May 2013, Santosh Shilimkar wrote: >>> From: Vaibhav Hiremath AM33XX only supports DT boot mode and with addition of extracting module resources like, irq, dma and address space from DT block, so now we can remove duplicate information from hwmod data file. >>> >>> OK, guess I'll take your word for it that it all works. The >>> BeagleBone-white with appended DTB hasn't booted here since v3.7. >>> And the BeagleBone-black with discrete DTB doesn't boot at all with >>> current mainline, only with the TI vendor kernel & DTB... >> >> Anyone care to shed light on what's missing for BeagleBone boot with >> mainline currently? > I have tested BeagleBone boot with today's mainline bootloader and > kernel. It boots perfectly fine. Can you post git trees + branch names (and/or commit IDs) and also kernel config please? Thanks, Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
Hi Paul, On Monday 10 June 2013 02:05 PM, Lokesh Vutla wrote: Hi Kevin, On Friday 07 June 2013 03:57 AM, Kevin Hilman wrote: Paul Walmsley writes: On Wed, 29 May 2013, Santosh Shilimkar wrote: From: Vaibhav Hiremath AM33XX only supports DT boot mode and with addition of extracting module resources like, irq, dma and address space from DT block, so now we can remove duplicate information from hwmod data file. OK, guess I'll take your word for it that it all works. The BeagleBone-white with appended DTB hasn't booted here since v3.7. And the BeagleBone-black with discrete DTB doesn't boot at all with current mainline, only with the TI vendor kernel & DTB... Anyone care to shed light on what's missing for BeagleBone boot with mainline currently? I have tested BeagleBone boot with today's mainline bootloader and kernel. It boots perfectly fine. I have taken the boot log for BeagleBone from the folllowing site: http://www.pwsan.com/omap/testlogs/test_v3.10-rc5/20130609031534/boot/am335xbone/ I have reset to your U-Boot commit id and took latest mainline kernel. It boots fine in my setup. You can find the logs here: http://pastebin.com/ggVYs3RG Thanks and regards, Lokesh Thanks and regards, Lokesh I've also not been able to boot a mainline kernel on the BeagleBone for some time. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
Hi Kevin, On Friday 07 June 2013 03:57 AM, Kevin Hilman wrote: Paul Walmsley writes: On Wed, 29 May 2013, Santosh Shilimkar wrote: From: Vaibhav Hiremath AM33XX only supports DT boot mode and with addition of extracting module resources like, irq, dma and address space from DT block, so now we can remove duplicate information from hwmod data file. OK, guess I'll take your word for it that it all works. The BeagleBone-white with appended DTB hasn't booted here since v3.7. And the BeagleBone-black with discrete DTB doesn't boot at all with current mainline, only with the TI vendor kernel & DTB... Anyone care to shed light on what's missing for BeagleBone boot with mainline currently? I have tested BeagleBone boot with today's mainline bootloader and kernel. It boots perfectly fine. Thanks and regards, Lokesh I've also not been able to boot a mainline kernel on the BeagleBone for some time. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
On Thursday 06 June 2013 06:27 PM, Kevin Hilman wrote: > Paul Walmsley writes: > >> On Wed, 29 May 2013, Santosh Shilimkar wrote: >> >>> From: Vaibhav Hiremath >>> >>> AM33XX only supports DT boot mode and with addition of >>> extracting module resources like, irq, dma and address space >>> from DT block, so now we can remove duplicate information from >>> hwmod data file. >> >> OK, guess I'll take your word for it that it all works. The >> BeagleBone-white with appended DTB hasn't booted here since v3.7. >> And the BeagleBone-black with discrete DTB doesn't boot at all with >> current mainline, only with the TI vendor kernel & DTB... > > Anyone care to shed light on what's missing for BeagleBone boot with > mainline currently? > > I've also not been able to boot a mainline kernel on the BeagleBone for > some time. > Looping Rajendra. Regards, Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
* Paul Walmsley [130605 21:06]: > On Wed, 29 May 2013, Santosh Shilimkar wrote: > > > From: Vaibhav Hiremath > > > > AM33XX only supports DT boot mode and with addition of > > extracting module resources like, irq, dma and address space > > from DT block, so now we can remove duplicate information from > > hwmod data file. > > OK, guess I'll take your word for it that it all works. The > BeagleBone-white with appended DTB hasn't booted here since v3.7. > And the BeagleBone-black with discrete DTB doesn't boot at all with > current mainline, only with the TI vendor kernel & DTB... > > Acked-by: Paul Walmsley Thanks applying into omap-for-v3.11/cleanup. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
Paul Walmsley writes: > On Wed, 29 May 2013, Santosh Shilimkar wrote: > >> From: Vaibhav Hiremath >> >> AM33XX only supports DT boot mode and with addition of >> extracting module resources like, irq, dma and address space >> from DT block, so now we can remove duplicate information from >> hwmod data file. > > OK, guess I'll take your word for it that it all works. The > BeagleBone-white with appended DTB hasn't booted here since v3.7. > And the BeagleBone-black with discrete DTB doesn't boot at all with > current mainline, only with the TI vendor kernel & DTB... Anyone care to shed light on what's missing for BeagleBone boot with mainline currently? I've also not been able to boot a mainline kernel on the BeagleBone for some time. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up
On Wed, 29 May 2013, Santosh Shilimkar wrote: > From: Vaibhav Hiremath > > AM33XX only supports DT boot mode and with addition of > extracting module resources like, irq, dma and address space > from DT block, so now we can remove duplicate information from > hwmod data file. OK, guess I'll take your word for it that it all works. The BeagleBone-white with appended DTB hasn't booted here since v3.7. And the BeagleBone-black with discrete DTB doesn't boot at all with current mainline, only with the TI vendor kernel & DTB... Acked-by: Paul Walmsley - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
