buzzmarshall has quit [Quit: Konversation terminated!]
ffhguy has joined #linux-amlogic
elastic_dog has quit [Ping timeout: 248 seconds]
elastic_dog has joined #linux-amlogic
ldevulder has joined #linux-amlogic
rockosov has joined #linux-amlogic
<ffhguy>
narmstrong Hello Neil Armstrong! My name is Arseniy, I'm from Dmitriy Rockosov's @rockosov team, i'm also working on upstreaming Amlogic code. I've got question about review of one of my MTD patch: https://lore.kernel.org/linux-mtd/20230501131025.754958-1-AVKrasnov@sberdevices.ru/T/#u I sent v1 on 26 April, then v2 and finally v3. But i didn't get any feedback since v1 (e.g. almost 1 month). So may be You know what to do in this case? Thanks
<narmstrong>
ffhguy: hi, I wasn't in CC to this, but it's not really amlogic related anyway, you should ping Miquel Raynal to know the state
naoki has joined #linux-amlogic
<ffhguy>
narmstrong, yes, it is not Amlogic driver. Ok, I'll try to ping Miquel Raynal again - last time I asked him 15 May, may be he is busy, because he reviewed me earlier.
<narmstrong>
ffhguy: it's a long week-end with some public holidays so i'm pretty sure I was off since last wednesday
<ffhguy>
narmstrong, aaa, ok, so for Macronix patch i'll ping Miquel Raynal. Thanks
<narmstrong>
ffhguy: same for this one, please ping him at the end of the week if no news
<rockosov>
narmstrong: Hello Neil! Do you happen to know of any specific channels on Libera or Freenode where we can discuss the patch series with Miquel? While the Micron patches may be minor, the meson NAND driver fixes are quite valuable. Currently, upstream has a non-working NAND driver for AXG, which is not ideal. We would appreciate any suggestions on how to proceed in this situation.
<rockosov>
narmstrong: ah, sorry, only now I see your message about public holiday. It may be a reason
<rockosov>
narmstrong: Sorry for the noise]\
<ffhguy>
narmstrong, ok, i'll ping him at the end of this week! Thank You
<narmstrong>
rockosov: he is on #armlinux on Libera as mraynal
<rockosov>
narmstrong: Thanks a lot!
f11f12 has joined #linux-amlogic
Daanct12 has quit [Remote host closed the connection]
Daanct12 has joined #linux-amlogic
JohnnyonF has joined #linux-amlogic
JohnnyonFlame has quit [Ping timeout: 240 seconds]
Daanct12 has quit [Ping timeout: 240 seconds]
Danct12 has joined #linux-amlogic
jacobk has quit [Ping timeout: 250 seconds]
f11f12 has quit [Quit: Leaving]
jacobk has joined #linux-amlogic
camus has quit [Ping timeout: 240 seconds]
camus has joined #linux-amlogic
jacobk has quit [Ping timeout: 240 seconds]
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #linux-amlogic
<minute>
trying to bring up rtw8822cs sdio module on bananapi (a311d). the module is found but: > meson-gx-mmc ffe03000.mmc: unaligned sg offset 2048 len 2
<minute>
"failed to download rsvd page", "failed to download firmware", etc, until "rtw_8822cs: probe of mmc2:0001:1 failed with error -16"
<minute>
in other news, returning false in dw_hdmi_support_scdc() is a workaround for my HDMI problem.
jacobk has joined #linux-amlogic
jacobk has quit [Ping timeout: 240 seconds]
<xdarklight>
minute: which kernel version? that looks like a warning and it should fall back to non-DMA transfers. however, 6.4-rc3 has a fix a len = 2 issue on Allwinner controllers, so I suggest re-trying with 6.4-rc3
<minute>
xdarklight: ah, currently Linux version 6.4.0-rc1+
<minute>
xdarklight: do you perhaps have a link to the patch? then i wouldn't need to rebase my WIP patchset
<xdarklight>
minute: it's a bit weird since until ~1 week ago I only used an Amlogic SM1 (S905X3) board for testing so I can't fully explain why yours seems to dislike the read16. I'd be happy if above patch fixes it also for you though
<minute>
xdarklight: oh cool, i will test it now
<minute>
xdarklight: that fixed it, no more errors!
<xdarklight>
minute: yay! :-)
<minute>
really nice. wifi works
<minute>
well, i was a bit quick to judge
<minute>
> [ 7779.821268] kernel BUG at net/core/skbuff.c:200!
<xdarklight>
minute: it's very weird because we've been seeing a similar problem when bringing up RTL8723DS support and came up with that fix: https://lore.kernel.org/linux-wireless/20230522202425.1827005-2-martin.blumenstingl@googlemail.com/ - while researching that we found that the vendor driver only has this check for older chipsets (802.11n, 802.11ac chips don't need that check according to the vendor driver...). you're the first one to hit that case
<xdarklight>
with a 802.11ac chip
<xdarklight>
anyway, I'm out for today. good night