8:20 a.m.
Good day,
will Fedora 30 support Raspberry Pi 4, or we must wait to Fedora 31?
With best regards,
Filip Bartmann
9:20 a.m.
Good day,
will Fedora 30 support Raspberry Pi 4, or we must wait to Fedora 31?
At the moment that is unknown. Fedora 31 will be the initial focus and
then once we know what the status is there I will be able to access
what the effort to get it running on F-30 will be and how much of a
support nightmare that would be.
I do the Raspberry Pi enablement and support primarily in my own time.
I now have a device that arrived an hour or so ago, I will start to
investigate the requirements this evening.
10:07 a.m.
Hi,
On 25.06.19 15:20, filbar(a)centrum.cz wrote:
Good day,
will Fedora 30 support Raspberry Pi 4, or we must wait to Fedora 31?
a short statement from myself as the BCM2835 maintainer. The sources has
been published yesterday. The BCM2835 feature window for Linux 5.3 is
closed since 3 weeks. So the first kernel with minimal RPi 4 support
could be 5.4.
Stefan
>
> With best regards,
> Filip Bartmann
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
11:58 a.m.
On 25.06.19 15:20, filbar(a)centrum.cz wrote:
> Good day,
> will Fedora 30 support Raspberry Pi 4, or we must wait to Fedora 31?
a short statement from myself as the BCM2835 maintainer. The sources has
been published yesterday. The BCM2835 feature window for Linux 5.3 is
closed since 3 weeks. So the first kernel with minimal RPi 4 support
could be 5.4.
Where is the upstream branches for 5.4 been published, from when I
pulled from the raspberrypi github sources late last night I didn't
see anything specific to the rpi4 I could see in any of the branches.
Peter
4:13 p.m.
Hi,
Am 25.06.19 um 18:58 schrieb Peter Robinson:
> On 25.06.19 15:20, filbar(a)centrum.cz wrote:
>> Good day,
>> will Fedora 30 support Raspberry Pi 4, or we must wait to Fedora 31?
> a short statement from myself as the BCM2835 maintainer. The sources has
> been published yesterday. The BCM2835 feature window for Linux 5.3 is
> closed since 3 weeks. So the first kernel with minimal RPi 4 support
> could be 5.4.
Where is the upstream branches for 5.4 been published, from when I
pulled from the raspberrypi github sources late last night I didn't
see anything specific to the rpi4 I could see in any of the branches.
as far as i know there isn't any upstream branch. Some of the RPi 4
stuff has been prepared for upstream (usually BCM2711 = downstream,
BCM2838 = upstream), but are buried in the rpi-4.19 branch.
Looks at this for example:
https://github.com/raspberrypi/linux/commits?author=pelwell
But there are also lot of hacks. Currently the biggest part on Kernel
side is the PCIe driver which isn't upstreamed yet. Another problem is
that there is no U-Boot support yet.
Without a real datasheet with register documentation this isn't fun ...
Stefan
Peter
4:42 p.m.
>>> Good day,
>>> will Fedora 30 support Raspberry Pi 4, or we must wait to Fedora 31?
>> a short statement from myself as the BCM2835 maintainer. The sources has
>> been published yesterday. The BCM2835 feature window for Linux 5.3 is
>> closed since 3 weeks. So the first kernel with minimal RPi 4 support
>> could be 5.4.
> Where is the upstream branches for 5.4 been published, from when I
> pulled from the raspberrypi github sources late last night I didn't
> see anything specific to the rpi4 I could see in any of the branches.
as far as i know there isn't any upstream branch. Some of the RPi 4
stuff has been prepared for upstream (usually BCM2711 = downstream,
BCM2838 = upstream), but are buried in the rpi-4.19 branch.
Looks at this for example:
https://github.com/raspberrypi/linux/commits?author=pelwell
But there are also lot of hacks. Currently the biggest part on Kernel
side is the PCIe driver which isn't upstreamed yet. Another problem is
that there is no U-Boot support yet.
I figured as much, I had looked at the 4.19.y branch as I figured
that's where the initial bits would be but I hadn't seen anything that
stood out :-/
I was looking through the DT compatible strings from
bcm2711-rpi-4-b.dtb and worked out the issues with the PCIe issue, I
figured there was either a new driver or enablement to one of the
other broadcom drivers, most of the rest looked like fairly generic
Arm IP or exisiting broadcom bits so my guess would there would be DT
plus probably some enablement bits for the new SoC to find.
Without a real datasheet with register documentation this isn't
fun ...
For you or the wider community?
Peter
1:37 a.m.
On 25.06.19 23:42, Peter Robinson wrote:
>>>> Good day,
>>>> will Fedora 30 support Raspberry Pi 4, or we must wait to Fedora 31?
>>> a short statement from myself as the BCM2835 maintainer. The sources has
>>> been published yesterday. The BCM2835 feature window for Linux 5.3 is
>>> closed since 3 weeks. So the first kernel with minimal RPi 4 support
>>> could be 5.4.
>> Where is the upstream branches for 5.4 been published, from when I
>> pulled from the raspberrypi github sources late last night I didn't
>> see anything specific to the rpi4 I could see in any of the branches.
> as far as i know there isn't any upstream branch. Some of the RPi 4
> stuff has been prepared for upstream (usually BCM2711 = downstream,
> BCM2838 = upstream), but are buried in the rpi-4.19 branch.
>
> Looks at this for example:
>
> https://github.com/raspberrypi/linux/commits?author=pelwell
>
> But there are also lot of hacks. Currently the biggest part on Kernel
> side is the PCIe driver which isn't upstreamed yet. Another problem is
> that there is no U-Boot support yet.
I figured as much, I had looked at the 4.19.y branch as I figured
that's where the initial bits would be but I hadn't seen anything that
stood out :-/
I was looking through the DT compatible strings from
bcm2711-rpi-4-b.dtb and worked out the issues with the PCIe issue, I
figured there was either a new driver or enablement to one of the
other broadcom drivers, most of the rest looked like fairly generic
Arm IP or exisiting broadcom bits so my guess would there would be DT
plus probably some enablement bits for the new SoC to find.
I will start to prepare
an initial RFC series in the near future. But
it's summer, so don't expect anything too soon.
> Without a real datasheet with register documentation this isn't fun ...
For you or the wider community?
For all
>
> Peter
3:16 a.m.
On 26.06.19 08:37, Stefan Wahren wrote:
On 25.06.19 23:42, Peter Robinson wrote:
>>>>> Good day,
>>>>> will Fedora 30 support Raspberry Pi 4, or we must wait to Fedora 31?
>>>> a short statement from myself as the BCM2835 maintainer. The sources has
>>>> been published yesterday. The BCM2835 feature window for Linux 5.3 is
>>>> closed since 3 weeks. So the first kernel with minimal RPi 4 support
>>>> could be 5.4.
>>> Where is the upstream branches for 5.4 been published, from when I
>>> pulled from the raspberrypi github sources late last night I didn't
>>> see anything specific to the rpi4 I could see in any of the branches.
>> as far as i know there isn't any upstream branch. Some of the RPi 4
>> stuff has been prepared for upstream (usually BCM2711 = downstream,
>> BCM2838 = upstream), but are buried in the rpi-4.19 branch.
>>
>> Looks at this for example:
>>
>> https://github.com/raspberrypi/linux/commits?author=pelwell
>>
>> But there are also lot of hacks. Currently the biggest part on Kernel
>> side is the PCIe driver which isn't upstreamed yet. Another problem is
>> that there is no U-Boot support yet.
> I figured as much, I had looked at the 4.19.y branch as I figured
> that's where the initial bits would be but I hadn't seen anything that
> stood out :-/
>
> I was looking through the DT compatible strings from
> bcm2711-rpi-4-b.dtb and worked out the issues with the PCIe issue, I
> figured there was either a new driver or enablement to one of the
> other broadcom drivers, most of the rest looked like fairly generic
> Arm IP or exisiting broadcom bits so my guess would there would be DT
> plus probably some enablement bits for the new SoC to find.
I will start to prepare an initial RFC series in the near future. But
it's summer, so don't expect anything too soon.
Just a short update: it will be a bumpy road :-(
The good news first: sdhci (incl. clk changes) and pinctrl are ready.
But there is hassle with DMA especially with current Linux 5.3 rc. So in
case the initial series land for Linux 5.4, there will be only debug
UART and no graphics support. Also i'm currently not sure arm64 support
will be ready.
7:07 a.m.
Hi Stefan,
Firstly thanks for your work here.
>>> But there are also lot of hacks. Currently the biggest
part on Kernel
>>> side is the PCIe driver which isn't upstreamed yet. Another problem is
>>> that there is no U-Boot support yet.
>> I figured as much, I had looked at the 4.19.y branch as I figured
>> that's where the initial bits would be but I hadn't seen anything that
>> stood out :-/
>>
>> I was looking through the DT compatible strings from
>> bcm2711-rpi-4-b.dtb and worked out the issues with the PCIe issue, I
>> figured there was either a new driver or enablement to one of the
>> other broadcom drivers, most of the rest looked like fairly generic
>> Arm IP or exisiting broadcom bits so my guess would there would be DT
>> plus probably some enablement bits for the new SoC to find.
> I will start to prepare an initial RFC series in the near future. But
> it's summer, so don't expect anything too soon.
>
Just a short update: it will be a bumpy road :-(
The good news first: sdhci (incl. clk changes) and pinctrl are ready.
But there is hassle with DMA especially with current Linux 5.3 rc. So in
case the initial series land for Linux 5.4, there will be only debug
UART and no graphics support. Also i'm currently not sure arm64 support
will be ready.
Is there a tracking ticket for the changes that need to be made,
issues etc. I noticed you posted a v2 series this morning. Is the
aarch64 issue the one with the dma32 problems or is there other issues
as well?
Peter
8:14 a.m.
Hi Peter,
On 14.08.19 14:07, Peter Robinson wrote:
Hi Stefan,
Firstly thanks for your work here.
>>>> But there are also lot of hacks. Currently the biggest part on Kernel
>>>> side is the PCIe driver which isn't upstreamed yet. Another problem
is
>>>> that there is no U-Boot support yet.
>>> I figured as much, I had looked at the 4.19.y branch as I figured
>>> that's where the initial bits would be but I hadn't seen anything
that
>>> stood out :-/
>>>
>>> I was looking through the DT compatible strings from
>>> bcm2711-rpi-4-b.dtb and worked out the issues with the PCIe issue, I
>>> figured there was either a new driver or enablement to one of the
>>> other broadcom drivers, most of the rest looked like fairly generic
>>> Arm IP or exisiting broadcom bits so my guess would there would be DT
>>> plus probably some enablement bits for the new SoC to find.
>> I will start to prepare an initial RFC series in the near future. But
>> it's summer, so don't expect anything too soon.
>>
> Just a short update: it will be a bumpy road :-(
>
> The good news first: sdhci (incl. clk changes) and pinctrl are ready.
>
> But there is hassle with DMA especially with current Linux 5.3 rc. So in
> case the initial series land for Linux 5.4, there will be only debug
> UART and no graphics support. Also i'm currently not sure arm64 support
> will be ready.
Is there a tracking ticket for the changes that need to be made,
issues etc.
BCM2711 / Raspberry Pi 4 support is too complex for a single ticket. I
decided to start with inital support (without GENET, thermal, HWRNG, USB
3.0, 40 bit DMA, V3D) and handle the advanced topics separate. But yes
there is a ticket for the initial support:
https://github.com/lategoodbye/rpi-zero/issues/43
I noticed you posted a v2 series this morning. Is the
aarch64 issue the one with the dma32 problems or is there other issues
as well?
Unfortunately they are completely different. Nicolas Saenz Julienne will
take care of them.
The good news: sdhci (without clock) and pinctrl changes has been merged
for Linux 5.4.
Stefan
>
> Peter
> _______________________________________________
> arm mailing list -- arm(a)lists.fedoraproject.org
> To unsubscribe send an email to arm-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/arm@lists.fedoraproject.org
1714
days inactive
1764
days old
9 comments
3 participants
participants (3)
-
filbar＠centrum.cz -
Peter Robinson -
Stefan Wahren