12.04.2017 11:44, Fabian Vogt пишет:
Hi,
as far as I can tell this is the usual issue with uboot that it really
relies on a serial console.
There is a patch on the u-boot mailing list that should fix this for
the rpi2 u-boot on rpi3 HW case:
https://patchwork.ozlabs.org/patch/746827/
Unfortunately, It doesn't work for me...
While it is not the main objective of the patch, as a side effect
it enables the uart autodetection for all RPi models, so it might
fix this case as well.
Cheers,
Fabian
Am Mittwoch, 12. April 2017, 10:30:31 CEST schrieb Alexander Graf:
Raspbian runs Linux straight away which then adapts to the respective
target board. U-Boot however does not; it statically compiles in which
target serial port to use.
I agree that this should probably be fixed :). Patches are more than
welcome!
Alex
On 12.04.17 10:23, Matwey V. Kornilov wrote:
Now it is clear, thank you. I though that the same raspbian image fitted
all RPI versions so JeOS did also.
12.04.2017 11:12, Alexander Graf пишет:
Hi,
I don't think it would work, as the serial port is behind a different
IP block.
Alex
Am 12.04.2017 um 09:17 schrieb Matwey V. Kornilov
<matwey.korni...@gmail.com>:
Hello,
Could somebody please tell me whether raspberrypi2 image supposed to
work on raspberrypi3 in armv7 mode?
I've just tried but I don't see anything on serial console, even
u-boot messages. Is it the image broken? I don't have raspberrypi2 to
test.
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
