From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: "Maciej W. Rozycki" <macro@mips.com>, Huacai Chen <chenhc@lemote.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
James Hogan <james.hogan@mips.com>,
"Steven J . Hill" <Steven.Hill@cavium.com>,
linux-mips@linux-mips.org, Fuxin Zhang <zhangfx@lemote.com>,
Zhangjin Wu <wuzhangjin@gmail.com>
Subject: Re: [PATCH V2 1/2] MIPS: Loongson64: Select ARCH_MIGHT_HAVE_PC_PARPORT
Date: Sat, 03 Mar 2018 15:08:39 +0800 [thread overview]
Message-ID: <1520060919.13983.3.camel@flygoat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1803021204250.10166@tp.orcam.me.uk>
在 2018-03-02五的 12:07 +0000，Maciej W. Rozycki写道：
> On Wed, 28 Feb 2018, Huacai Chen wrote:
>
> > diff --git a/arch/mips/loongson64/Kconfig
> > b/arch/mips/loongson64/Kconfig
> > index bc2fdbf..12812a8b 100644
> > --- a/arch/mips/loongson64/Kconfig
> > +++ b/arch/mips/loongson64/Kconfig
> > @@ -7,6 +7,7 @@ choice
> > config LEMOTE_FULOONG2E
> > bool "Lemote Fuloong(2e) mini-PC"
> > select ARCH_SPARSEMEM_ENABLE
> > + select ARCH_MIGHT_HAVE_PC_PARPORT
> > select CEVT_R4K
> > select CSRC_R4K
> > select SYS_HAS_CPU_LOONGSON2E
>
> Hmm, I don't think the Fuloong(2e) machine has a parallel port
> connector.
> The chipset may support the port, but with no external connection I
> think
> there's no point in enabling it. Or am I missing something?
Thanks for your advice.
Some other Loongson-2E devices share the same kernel entry with
Fuloong-2E.
And the 2E desktop PC has a parallel port. So we enable it for these
devices.
>
> Maciej
>
--
Jiaxun Yang <jiaxun.yang@flygoat.com>
next prev parent reply other threads:[~2018-03-03 7:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 2:37 [PATCH V2 1/2] MIPS: Loongson64: Select ARCH_MIGHT_HAVE_PC_PARPORT Huacai Chen
2018-03-01 2:37 ` [PATCH V2 2/2] MIPS: Loongson64: Select ARCH_MIGHT_HAVE_PC_SERIO Huacai Chen
2018-03-02 12:07 ` [PATCH V2 1/2] MIPS: Loongson64: Select ARCH_MIGHT_HAVE_PC_PARPORT Maciej W. Rozycki
2018-03-02 12:07 ` Maciej W. Rozycki
2018-03-03 7:08 ` Jiaxun Yang [this message]
2018-03-03 9:38 ` Maciej W. Rozycki
2018-03-03 9:38 ` Maciej W. Rozycki
2018-03-05 10:03 ` James Hogan
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=1520060919.13983.3.camel@flygoat.com \
--to=jiaxun.yang@flygoat.com \
--cc=Steven.Hill@cavium.com \
--cc=chenhc@lemote.com \
--cc=james.hogan@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@mips.com \
--cc=ralf@linux-mips.org \
--cc=wuzhangjin@gmail.com \
--cc=zhangfx@lemote.com \
/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.