From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] who would say
Date: Tue, 22 Dec 2020 21:54:56 +0100 [thread overview]
Message-ID: <47E61A62614FA91D66A3F9A68FA7C9FF@felloff.net> (raw)
In-Reply-To: <d2ef001d-391a-8a1a-7696-a557c70204fc@gmail.com>
afaik, theres still no documentation available at all
for the genet in bcm2711 soc.
so everyone just copies what the linux driver does as
closely as possible. which means, once you have problems,
you have no idea if it is because you are *not* implementing
some unneccesary special hw offload feature the linux
driver uses or not...
frustrating, especially if you got problems like these:
https://github.com/raspberrypi/firmware/issues/1219
and then you get comments like:
"I suppose suggesting using Linux is not helpfull?"
and you know, they have all the secret datasheets...
anyway, not proud of that driver...
--
cinap
prev parent reply other threads:[~2020-12-22 21:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 19:03 Iruatã Souza
2020-12-22 19:12 ` sl
2020-12-22 19:21 ` Stuart Morrow
2020-12-22 21:04 ` cinap_lenrek
2020-12-22 19:39 ` hiro
2020-12-22 20:24 ` Iruatã Souza
2020-12-22 20:54 ` cinap_lenrek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47E61A62614FA91D66A3F9A68FA7C9FF@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).