On Jul 10, 2012, at 7:25 AM, Tabi Timur-B04825 wrote:
On Tue, Jul 10, 2012 at 3:39 AM, Xu Jiucheng jiucheng...@freescale.com
wrote:
Create the dts files for each core and splits the devices between
the two cores for P1021RDB-PC.
Core0 has l2, serial0, i2c, spi, gpio, tdm,dma, usb, eth0,
Kumar Gala wrote:
Since we already have P1021RDB-PC w/AMP support in upstream I agree we don't
need another example on P1021RDB-PC.
Would you accept a patch that removes all AMP device trees from upstream?
I just don't think that these very customer-specific dts files belong
upstream.
--
Kumar Gala wrote:
Since we already have P1021RDB-PC w/AMP support in upstream I agree
we don't need another example on P1021RDB-PC.
Would you accept a patch that removes all AMP device trees from upstream?
I just don't think that these very customer-specific dts files belong
upstream
[]
On Jul 11, 2012, at 9:49 AM, Timur Tabi wrote:
Kumar Gala wrote:
Since we already have P1021RDB-PC w/AMP support in upstream I agree we don't
need another example on P1021RDB-PC.
Would you accept a patch that removes all AMP device trees from upstream?
I just don't think that these very
Schneider, Kolja wrote:
Is there any alternate source for AMP device trees? Just in case someone
needs some sort of documentation?
The SDK. We can put a hundred AMP device trees on there if we want, and
no one will complain.
--
Timur Tabi
Linux kernel developer at Freescale
Kumar Gala wrote:
No, I think we should have at least one or two examples of AMP dts in
upstream.
We have more than that:
./p2020rdb_camp_core1.dts
./p1020rdb-pc_camp_core1.dts
./mpc8572ds_camp_core1.dts
./p2020rdb_camp_core0.dts
./p1020rdb-pc_camp_core0.dts
./mpc8572ds_camp_core0.dts
On Jul 11, 2012, at 9:56 AM, Timur Tabi wrote:
Kumar Gala wrote:
No, I think we should have at least one or two examples of AMP dts in
upstream.
We have more than that:
./p2020rdb_camp_core1.dts
./p1020rdb-pc_camp_core1.dts
./mpc8572ds_camp_core1.dts
./p2020rdb_camp_core0.dts
Kumar Gala wrote:
./p2020rdb_camp_core1.dts
./p1020rdb-pc_camp_core1.dts
./mpc8572ds_camp_core1.dts
./p2020rdb_camp_core0.dts
./p1020rdb-pc_camp_core0.dts
./mpc8572ds_camp_core0.dts
./p1020rdb_camp_core1.dts
./p1020rdb_camp_core0.dts
I'd be ok if we want to drop the p1020rdb as that
On Jul 11, 2012, at 10:53 PM, Tabi Timur-B04825 wrote:
Kumar Gala wrote:
./p2020rdb_camp_core1.dts
./p1020rdb-pc_camp_core1.dts
./mpc8572ds_camp_core1.dts
./p2020rdb_camp_core0.dts
./p1020rdb-pc_camp_core0.dts
./mpc8572ds_camp_core0.dts
./p1020rdb_camp_core1.dts
Create the dts files for each core and splits the devices between
the two cores for P1021RDB-PC.
Core0 has l2, serial0, i2c, spi, gpio, tdm,dma, usb, eth0, eth1,
sdhc, crypto, global-util, message, pci0, pci1, msi, crypto.
Core1 has l2, serial1, eth2.
Signed-off-by: Xu Jiucheng
On Tue, Jul 10, 2012 at 3:39 AM, Xu Jiucheng jiucheng...@freescale.com wrote:
Create the dts files for each core and splits the devices between
the two cores for P1021RDB-PC.
Core0 has l2, serial0, i2c, spi, gpio, tdm,dma, usb, eth0, eth1,
sdhc, crypto, global-util, message, pci0, pci1, msi,
On 07/10/2012 03:39 AM, Xu Jiucheng wrote:
+ crypto@3 {
+status = disabled;
+};
Whitespace.
+
+ mpic: pic@4 {
+ protected-sources =
+ 16 /* ecm, mem, L2, pci0,
12 matches
Mail list logo
