> The very last line is wrong.
> ifconfig eth0 192.168.1.4 up
Typo. It was fixed after few hours I created the gist.
> You should put the IP address on the bridge, not the master
> device eth0.
> ip addr add 192.168.1.4/24 dev br0
Noted. Thank you.
> FYI: ifconfig has been deprecated for maybe
> I wrote my (very first) public GIST about that. Please, could you
> review it, and point to the any logical bugs in there?
> https://gist.github.com/ZoranStojsavljevic/423b96e2ca3bd581f7ce417cb410c465
The very last line is wrong.
ifconfig eth0 192.168.1.4 up
You should put the IP address on th
Hello Andrew,
I see dead people... Really i do! After your reply.
> This happens when the driver is missing a resource during probe. It
> returns the error -EPROBE_DEFER, and the linux driver core will try
> the probe again later. Probably the second time all the resources it
> needs will be pre
On Sat, Sep 28, 2019 at 01:00:43AM +0200, Zoran Stojsavljevic wrote:
> Hello Andrew,
>
> > You should not need any kernel patches for switch side RGMII
> > delays. rgmii-id in the DT for the switch CPU port should be enough.
> > Some of the vf610-zii platforms use it.
>
> It should, but it does N
Hello Andrew,
> You should not need any kernel patches for switch side RGMII
> delays. rgmii-id in the DT for the switch CPU port should be enough.
> Some of the vf610-zii platforms use it.
It should, but it does NOT work. IT is clearly stated in port.c, in f-n:
static int mv88e6xxx_port_set_rgmi
On Thu, Sep 26, 2019 at 03:23:48PM +0200, Zoran Stojsavljevic wrote:
> Hello Andrew,
>
> I would like to thank you for the reply.
>
> I do not know if this is the right place to post such the questions,
> but my best guess is: yes.
>
> Since till now I did not make any success to make (using DSA
Hello Andrew,
I would like to thank you for the reply.
I do not know if this is the right place to post such the questions,
but my best guess is: yes.
Since till now I did not make any success to make (using DSA driver)
make mv88e6190 single switch to work with any kernel.org. :-(
I did ugly wo
> We have the configuration problem with the Marvell 88E6190 switch.
> What the our problem is... Is the switch is NOT configured with the
> EEPROM (24C512), which does not exist on the board.
That is pretty normal. If there is a EEPROM, i generally recommend it
is left empty. We want Linux to con
Hello Community,
We have interesting problem to solve using our HW platform. And I hope
somebody has the similar example, and some patches, which need to be
applied to the kernel (directory .../drivers/net/dsa/) to make this
application to work.
We have the configuration problem with the Marvell
