From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Olliver Schinagl <oliver@schinagl.nl>
Cc: Sander Vanheule <sander@svanheule.net>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mips: Realtek RTL: select NO_EXCEPT_FILL
Date: Sun, 19 Feb 2023 11:31:12 +0100 [thread overview]
Message-ID: <20230219103112.GA4095@alpha.franken.de> (raw)
In-Reply-To: <54238ab7-b7c0-a3a3-38e9-f7879866fb3c@schinagl.nl>
On Sun, Feb 19, 2023 at 10:27:17AM +0100, Olliver Schinagl wrote:
> It's still odd though; as we do not have _anything_ PCI, but it
> SWAP_IO_SPACE causes the crash.
but something uses readX/write() calls. If you aren't using any driver
existing driver but only newly written dedicated for that SOC
you could use raw_read/raw_writeX() instead. These type of functions
are always using native endianess.
> What makes SWAP_IO_SPACE generic then? :)
als long as hardware presents memory used with readX/writeX is
seen as little endian independant from CPU endianess it's generic.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2023-02-19 10:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 12:19 [PATCH] mips: Realtek RTL: select NO_EXCEPT_FILL Sander Vanheule
2023-01-27 16:27 ` Thomas Bogendoerfer
2023-01-28 14:39 ` Olliver Schinagl
2023-02-05 16:19 ` Thomas Bogendoerfer
2023-02-05 18:33 ` Olliver Schinagl
2023-02-17 17:37 ` Thomas Bogendoerfer
2023-02-17 19:27 ` Olliver Schinagl
2023-02-19 9:02 ` Thomas Bogendoerfer
2023-02-19 9:27 ` Olliver Schinagl
2023-02-19 10:31 ` Thomas Bogendoerfer [this message]
2023-02-19 16:07 ` Olliver Schinagl
2023-02-22 15:23 ` Olliver Schinagl
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=20230219103112.GA4095@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=oliver@schinagl.nl \
--cc=sander@svanheule.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