>> I captured a ping from my device to my computer to look if outgoing is
>> working
>> (captured on both devices). Here is the output from my device where i
>> started the:
>>
>> 00:24:24.752057 ARP, Request who-has 192.168.10.2 tell 192.168.10.1, length
>> 28
>> 0x: 0001 0800 0604
> I captured a ping from my device to my computer to look if outgoing is working
> (captured on both devices). Here is the output from my device where i started
> the:
>
> 00:24:24.752057 ARP, Request who-has 192.168.10.2 tell 192.168.10.1, length 28
> 0x: 0001 0800 0604 0001 6a2a ad79
> On Tue, Jun 11, 2019 at 09:36:16AM +0200, Benjamin Beckmeyer wrote:
So all ports are now in forwarding mode (Switch port register 0x4 of all
ports
are 0x7f), but I don't reach it over ping.
>>> Hi
>>>
>>> The most common error for people new to DSA is forgetting to bring
>>> the
On Tue, Jun 11, 2019 at 09:36:16AM +0200, Benjamin Beckmeyer wrote:
> >> So all ports are now in forwarding mode (Switch port register 0x4 of all
> >> ports
> >> are 0x7f), but I don't reach it over ping.
> > Hi
> >
> > The most common error for people new to DSA is forgetting to bring
> > the ma
>> So all ports are now in forwarding mode (Switch port register 0x4 of all
>> ports
>> are 0x7f), but I don't reach it over ping.
> Hi
>
> The most common error for people new to DSA is forgetting to bring
> the master interface up.
>
> The second thing to understand is that by default, all inte
> So all ports are now in forwarding mode (Switch port register 0x4 of all
> ports
> are 0x7f), but I don't reach it over ping.
Hi
The most common error for people new to DSA is forgetting to bring
the master interface up.
The second thing to understand is that by default, all interfaces are
s
On 06.06.19 15:59, Andrew Lunn wrote:
> On Thu, Jun 06, 2019 at 03:47:06PM +0200, Benjamin Beckmeyer wrote:
>> On 06.06.19 15:35, Andrew Lunn wrote:
>From our hardware developer I know now that we are using a "mini" SFF
which has no i2c eeprom.
>>> O.K. Does this mini SFF have LOS, TX
On Thu, Jun 06, 2019 at 03:47:06PM +0200, Benjamin Beckmeyer wrote:
>
> On 06.06.19 15:35, Andrew Lunn wrote:
> >> >From our hardware developer I know now that we are using a "mini" SFF
> >> which has no i2c eeprom.
> > O.K. Does this mini SFF have LOS, TX-Disable, etc? Are these connected
> > t
On 06.06.19 15:35, Andrew Lunn wrote:
>> >From our hardware developer I know now that we are using a "mini" SFF
>> which has no i2c eeprom.
> O.K. Does this mini SFF have LOS, TX-Disable, etc? Are these connected
> to GPIOs? I assume the SFF is fibre? And it needs the SERDES to speak
> 1000Base
> >From our hardware developer I know now that we are using a "mini" SFF
> which has no i2c eeprom.
O.K. Does this mini SFF have LOS, TX-Disable, etc? Are these connected
to GPIOs? I assume the SFF is fibre? And it needs the SERDES to speak
1000BaseX, not SGMII?
> Switch
On 06.06.19 14:24, Andrew Lunn wrote:
> On Thu, Jun 06, 2019 at 10:49:08AM +0200, Benjamin Beckmeyer wrote:
I removed all phy-handle for the internal ports and in the mdio part
is only port 2 and 6 by now. But the Serdes ports are still not be
recognized. So maybe there is still s
>> I removed all phy-handle for the internal ports and in the mdio part
>> is only port 2 and 6 by now. But the Serdes ports are still not be
>> recognized. So maybe there is still something wrong?
> What do you mean by SERDES? Do you mean they are connected to an SFP
> cage? If so, you need to ad
> I removed all phy-handle for the internal ports and in the mdio part
> is only port 2 and 6 by now. But the Serdes ports are still not be
> recognized. So maybe there is still something wrong?
What do you mean by SERDES? Do you mean they are connected to an SFP
cage? If so, you need to add an S
>> Here is my device tree
>>
>> mdio {
>> #address-cells = <1>;
>> #size-cells = <0>;
>>
>> switch0: switch0@0 {
>> compatible = "marvell,mv88e6085";
>> reg = <0x0>;
>> pinctrl-0
> Here is my device tree
>
> mdio {
> #address-cells = <1>;
> #size-cells = <0>;
>
> switch0: switch0@0 {
> compatible = "marvell,mv88e6085";
> reg = <0x0>;
> pinctrl-0 = <&lcd
>> I got the devicetree from somebody that is why German is in it. But
>> first I wanted to get it running before I tidy it up. The switch is
>> strapped to single mode (so I can read SMI addresses 0x10-0x16 and
>> 0x1b-0x1e directly).
> Hi Benjamin
>
> You have miss-understood what reg means.
>
>
> I got the devicetree from somebody that is why German is in it. But
> first I wanted to get it running before I tidy it up. The switch is
> strapped to single mode (so I can read SMI addresses 0x10-0x16 and
> 0x1b-0x1e directly).
Hi Benjamin
You have miss-understood what reg means.
There are
Hey Andrew,
thanks for you reply.
I got the devicetree from somebody that is why German is in it. But first I
wanted to get it running before I tidy it up.
The switch is strapped to single mode (so I can read SMI addresses 0x10-0x16
and 0x1b-0x1e directly). Do I have to
tell this the devicetree?
On Tue, Jun 04, 2019 at 03:07:25PM +0200, Benjamin Beckmeyer wrote:
> Hi all,
>
> I'm working on a custom board with a 88E6321 and an i.MX28. Port 5 is
> directly connected per RMII to the CPU.
> The switch is running in CPU attached mode. On Port 2 and 6 we have 2
> external Micrel KSZ9031 PHY
19 matches
Mail list logo
