9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Porting RTL8111 (ether8169) driver to bcm64
Date: Sun, 14 Nov 2021 06:31:01 +0100	[thread overview]
Message-ID: <62D93F1A2C6C5AFCD034D1DDEFB31C65@felloff.net> (raw)
In-Reply-To: <0100017d1b4e37b3-3803a9cc-799e-4bbc-bd38-539fad5e750c-000000@email.amazonses.com>

> Are there already similar calls in 9front and I’ve (stupidly) overlooked them? 

no. i/o space is not supported on arm. this has nothing todo
with 9front.

i'm pretty sure the rtl chip will provide a membar with memory
mapped registers in addition to the i/o port interface,
you do not need special calls for this.

just vmap() the and access the registers with loads and stores.

get the datasheet and programmers manual for the rtl chip.

> Should it be as simple as adding the platform dependent calls in the driver
> to get it to work on the Pi, or is there more work that needs to be done to
> the bcm64 PCIe interface?

for dma, you need to manually keep the caches coherent with
the device using dmaflush() calls (see in port/usbxhci.c as an example).

this is the biggest reason most drivers cannot direcly be used
on arm, tho shouldnt be too difficult to make it work.

--
cinap

  reply	other threads:[~2021-11-14  5:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-13 21:57 Mack Wallace
2021-11-14  5:31 ` cinap_lenrek [this message]
2021-11-14  5:57 ` cinap_lenrek
2021-11-22 22:01   ` Mack Wallace
2021-11-24 11:41     ` cinap_lenrek
2021-12-07 20:41       ` Mack Wallace

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=62D93F1A2C6C5AFCD034D1DDEFB31C65@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).