From: Linus Walleij <linus.walleij@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
Imre Kaloz <kaloz@openwrt.org>,
Krzysztof Halasa <khalasa@piap.pl>,
Rod Whitby <rod@whitby.id.au>, Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH] ARM: dts: ixp4xx: Add a devicetree for Freecom FSG-3
Date: Fri, 30 Jul 2021 14:21:40 +0200 [thread overview]
Message-ID: <CACRpkdYL3SZeYoZYKye9rjXNVcsE25oavkJHNYHKH-sEuJFDpA@mail.gmail.com> (raw)
In-Reply-To: <YQLMikcayVvaeBAx@lunn.ch>
On Thu, Jul 29, 2021 at 5:43 PM Andrew Lunn <andrew@lunn.ch> wrote:
>
> > + /* EthB */
> > + ethernet@c8009000 {
(...)
> https://usermanual.wiki/Freecom-Technologies/FreecomTechnologiesFsg3UsersManual552148.1686484831/view
>
> This appears to also have an Ethernet switch. So is suspect this is
> also wrong in the same way.
In this case I am literally translating the existing board file:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/mach-ixp4xx/fsg-setup.c
It appears to have been working for years, I strongly suspect that
the switch operates fine due to boot-time default set-up, and when
we start using this phy the static configuration of the switch will
deal with the switching.
Marc has this device and seemed to be merrily poking at it to
install a UART so if he gets it running he could confirm if the
switch works out of the box like this.
Yours,
Linus Walleij
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-30 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 14:41 [PATCH] ARM: dts: ixp4xx: Add a devicetree for Freecom FSG-3 Linus Walleij
2021-07-29 15:43 ` Andrew Lunn
2021-07-30 12:21 ` Linus Walleij [this message]
2021-07-30 12:33 ` Marc Zyngier
2021-08-01 13:22 ` Marc Zyngier
2021-08-01 13:55 ` Andrew Lunn
2021-08-01 18:59 ` Marc Zyngier
2021-08-02 22:05 ` Linus Walleij
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=CACRpkdYL3SZeYoZYKye9rjXNVcsE25oavkJHNYHKH-sEuJFDpA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andrew@lunn.ch \
--cc=kaloz@openwrt.org \
--cc=khalasa@piap.pl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=rod@whitby.id.au \
/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).