Hello all and sorry for pinging in late into this conversation.
First of all, as someone who noticed the original issue but never got
around to properly report or investigate it, a big thanks go to the
people here who have been devoting time and effort trying to get to the
bottom of it, and
Hi Wookey,
Thanks a lot for looking into this!
On 2021.05.14 03:08, Wookey wrote:
I've done this, and if you want to test the mini.iso image at:
http://wookware.org/software/rpi4-test.iso
That would be good. (I don't have an rpi4 to test on)
Just tested it, and I can confirm it fixes the
For reference I have submitted a new pull request against src:linux that
attempts to fix this in
https://salsa.debian.org/kernel-team/linux/-/merge_requests/350
As people who monitor the Debian ARM64 mailing list should be aware,
this is a rather major issue, that people wanting to install
On 2020.05.09 22:20, Ben Hutchings wrote:
On Thu, 2020-05-07 at 14:23 +0100, Pete Batard wrote:
[...]
I specifically designed the patch I submitted for easy review and
integration, because there are missing elements from 4.x that are
present in 5.x, that we have to compensate for. I would
On 2020.05.07 13:45, Ben Hutchings wrote:
Also, there would be no point in enabling this driver in 4.19, only to
have people find on upgrade to the next version on Debian that we
didn't enable it there. That's why we're concerned with both versions.
Yes, I did consider that, but I feel that
I would really like to get an update on this, because I really can't
understand what the holdup is, or why non related issues seem to be be
shoved into this bug, with the apparent end result of completely
distracting from the matter at hand.
This bug is about one thing and one thing only:
Does that mean that the next Debian ISO installer will use Linux kernel
5.5.13.1 or later?
Because, if that is not the case, this bug is certainly not fixed at all
and must be reopened.
To reiterate, the problem is that the official netinst ISO cannot
perform a network installation of the
Just going to point out that the 5.x equivalent patch has now been
applied to Linux mainline as per:
https://lkml.kernel.org/lkml/20200224.153146.125327154283545636.da...@davemloft.net/
Could we get some acknowledgement that this patchset is being looked at
for possible integration and isn't
Foundation
declares the network interface (though using it as such in a 4.19 kernel
will require the provision of the "brcm,max-dma-burst-size" attribute).
Signed-off-by: Pete Batard
---
.../net/ethernet/broadcom/genet/bcmgenet.c| 74 ++-
drivers/net/ethernet
Just gonna add that the latest UEFI Firmware, released today at
https://github.com/pftf/RPi4/releases, now contains all the elements
needed (ACPI binding and UMAC initialization) for the above patch to work.
Which means that, the only limiting factor for UEFI Debian 10.x netinst
on a
the provision of the "brcm,max-dma-burst-size" attribute).
Signed-off-by: Pete Batard
---
.../net/ethernet/broadcom/genet/bcmgenet.c| 74 ++-
drivers/net/ethernet/broadcom/genet/bcmmii.c | 33 -
drivers/net/phy/mdio-bcm-unimac.c | 26 ++-
3 files ch
11 matches
Mail list logo
