Playing with Play-Doh

[hns]

That doesn't work on ARM, you always need an entirely new kernel specially build for your target platform even before you need to worry about drivers. Work has been done to change that, but it isn't of any use in this case AFAIK.

Not any more since ca. Linux 3.14 (where they introduced DT for ARM).
You just need a different "device tree" file which is more or less a compiled hardware description. The uImage/zImage and the kernel modules are quite universal nowadays and can be swapped around.
The Pyra currently uses the "Letux" kernel which also runs on the OpenPandora. And they are different ARM (OMAP3 vs. OMAP5).
So you just need to make U-Boot load either pyra.dtb or pandora.dtb and the otherwise identical system image boots on both. Unless you use special features of one SoC the other one doesn't have.

 

[klapse]

hns's location is so appropriate

 

[waGL]

Oberhaching? More like Uberhacking :-D

 

[Zwerg01]

I think this is the point of having the modular CPU boards, also I think developing a new replacement 2.0 board for the pyra will be easier once they're out in the wild.
[...]
I feel the only thing that could mess up the CPU board is an archeticture change from ARM to x86, but doing so would also ruin our community's software repository, let alone the Pyra OS.

I am not well versed with this field of development, but that is my uneducated blue collar pleb opinion.

You build a hardware plattform around the CPU and not vice versa. it is nearly impossible to find a CPU that can replace the old one. other architecture has other voltages, current draw, thermal dissipation. and then it has to have the same features like emmc controller, image rotation, MIPI for 3G/4G etc etc...

I didn't found information about qualification of the OMAP5. So if it is only for consumer application, it is very likely that it is discontinued soon.
[doublepost=1499031992,1499031886][/doublepost]

ED already has thousands of them in stock at the fab plant, IIRC,

How many exaclty? Where did you get your information.

 

[Letalis Sonus]

like emmc controller

You mean for the eMMC chip that is part of the CPU board and therefore totally replaceable?

MIPI for 3G/4G etc etc...

MIPI covers a lot of interfaces, but the PLS8 chips use USB. I'm pretty sure we only need DSI.

I didn't found information about qualification of the OMAP5. So if it is only for consumer application, it is very likely that it is discontinued soon.

In contrast to OMAP3, OMAP5 was especially targeting the industrial and automotive market IIRC, if they've got even a single customer in that field it won't go out of production for a loooong time. The platform is already discontinued, but it should have a pretty satisfactory guaranteed availability.

 

[Zwerg01]

You mean for the eMMC chip that is part of the CPU board and therefore totally replaceable?

I said emmc controller, not emmc chip.

Renesas automotive mcu introduced 2011 is d'cont last year. Place last order until 2018. loooooooooonnnnnngggggg time. lol. It is always depending on the policy of manufacturer.

 

[Silent-Hunter]

The eMMC and CPU are on the CPU board, if there is an external eMMC controller I'm sure it's on the same board too. There would be no reason to have it on the main board.

 

[Grench]

I said emmc controller, not emmc chip.

Renesas automotive mcu introduced 2011 is d'cont last year. Place last order until 2018. loooooooooonnnnnngggggg time. lol. It is always depending on the policy of manufacturer.

Renesas now has their own SoC too. Check their H3 dev unit. ARM powerhouse.

 

[TrashyMG]

I said emmc controller, not emmc chip.

Renesas automotive mcu introduced 2011 is d'cont last year. Place last order until 2018. loooooooooonnnnnngggggg time. lol. It is always depending on the policy of manufacturer.

The eMMC controller is built into the SoC, so yet again it's still replaceable.

 

[Grench]

@EvilDragon &/or @hns

The Pyra Wiki information on SoC/CPU board revisions is pretty sparse. When you communicate with each other, what designations do you use to differentiate the versions? I'm betting others might find this information interesting as well.

What I had hoped to find in the Pyra Wiki was:
Board revision/designation/identifier:
Date PCB manufactured:
Quantity manufactured:
Date first populated:
Short blurb about characteristics (good/bad/other):

Thank you!

 

[Xcl4m4t10n]

 

[Inqui]

Noooooooooo
Up to five days for arriving and writing :-/

 

[EvilDragon]

@EvilDragon &/or @hns

The Pyra Wiki information on SoC/CPU board revisions is pretty sparse. When you communicate with each other, what designations do you use to differentiate the versions? I'm betting others might find this information interesting as well.

What I had hoped to find in the Pyra Wiki was:
Board revision/designation/identifier:
Date PCB manufactured:
Quantity manufactured:
Date first populated:
Short blurb about characteristics (good/bad/other):

Thank you!

We have different board revisions, hns should know all about them.


Sent from my XT1650-03 using Tapatalk

 

[Askarus]

Who cares about Keymats.
It's good already.

 

[ClockworkCoder]

Who cares about Keymats.
It's good already.

ED's too busy sculpting things in play-doh methinks.

 

[driftke70]

Nice. Im GM of a company in Australia that manufactures PVC for a living for people like you.

I think you guys are looking too far into this. The device will be more about how you use it.

 

[Binky]

Nice. Im GM of a company in Australia that manufactures PVC for a living for people like you.

What's that have to do with the price of fish?

 

[Klumpen]

What's that have to do with the price of fish?

 

[driftke70]

Some guy was talking about working with pvc and my phone didnt quote for some reason.

Im sorry for bringing confusion into your life

 

[Grench]

Some guy was talking about working with pvc and my phone didnt quote for some reason.

Im sorry for bringing confusion good humor into your life