9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: <tlaronde@kergis.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Ethernet, PCI and OCP
Date: Mon, 7 Apr 2025 19:10:27 +0200	[thread overview]
Message-ID: <Z_QHA8pAOSWC97uI@kergis.com> (raw)

I'm currently trying to augment the ether8169 driver to support
Realtek 8125 and 8126.

It's a mess and a maze (I'm working with the Realtek published driver
for FreeBSD, due to the license). [But I will probably swith to the
NetBSD/OpenBSD driver, that has the same king of license, but is far
more understandable. The Linux one is daunting as well...]

If I can untangle what is added for support of different archs,
alignments, endianness, threads, handling of buffer, DMA and so on, I'm
(more than) a bit puzzled with what concerns OCP.

From a very cursory look, OCP seems to be both a hardware feature
(smaller cards for servers) and additional software capabilities
(dealing with hardware acceleration).

There is a bunch of code dealing with OCP concurrently with "normal"
config done as usual via mapped registers---and I'm trying to get the
config right.

Has anybody some clue about the question of ignoring absolutely anything
having to deal with OCP (things will work even if not with optional
hardware acceleration)?
-- 
        Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
                     http://www.kergis.com/
                    http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T0a21e644fc69840f-M9bd23fa5f7008f1d85922753
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

                 reply	other threads:[~2025-04-07 17:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Z_QHA8pAOSWC97uI@kergis.com \
    --to=tlaronde@kergis.com \
    --cc=9fans@9fans.net \
    /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).