All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 17 Feb 2023 18:37:08 +0100	[thread overview]
Message-ID: <20230217173708.GA14134@alpha.franken.de> (raw)
In-Reply-To: <f9c1be9c-478e-55e8-ad34-370641181015@schinagl.nl>

On Sun, Feb 05, 2023 at 07:33:46PM +0100, Olliver Schinagl wrote:
> > I always thought that SWAP_IO_SPACE is needed for big endian, but
> > looking at arch/mips/Kconfig I see a lot of SWAP_IO_SPACE for pure
> > little endian machines. I need to dig deeper to understand why.
> Thank you!

and the reason why this works is simple, CONFIG_SWAP_IO_SPACE is a nop
for little endian.

> > such a change would defeat the generic part of GENERIC_MIPS_KERNEL,
> > because it will then only work on REALTEC_SOC and nothing else.
> Ignoring the potential incorrect detail here, obviously I would prefer to
> use the GENERIC_MIPS_KERNEL, but having to copy the whole config just to
> leave out that one option also is kinda meh. So i'm hoping we can find a
> solution of course :)

what SOC is this exactly ? Do you have a programmers manual for it,
which contains details about the PCI bridge ? Most of the PCI bridges
used for MIPS contain a bit to select the endianess of the access
to PCI spaces. If there is such a config just changing the current
setting, should solve your problem.

If this isn't possible you could use something similair to the
INGENIC approach, which could use a generic kernel but also an
customized kernel. And in such a customized kernel it should be
possible to remove SWAP_IO_SPACE.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2023-02-17 17:37 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 [this message]
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
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=20230217173708.GA14134@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.