From: Eric Miao <eric.y.miao@gmail.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: linux-arm-kernel@lists.arm.linux.org.uk,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
samuel@sortiz.org, netdev@vger.kernel.org,
Alexander Beregalov <a.beregalov@gmail.com>
Subject: Re: [PATCH] pxaficp-ir - remove incorrect net_device_ops
Date: Tue, 28 Jul 2009 11:01:14 +0800 [thread overview]
Message-ID: <4A6E69FA.9010903@gmail.com> (raw)
In-Reply-To: <200907240257.10906.marek.vasut@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1473 bytes --]
Marek Vasut wrote:
> Hi!
>
> This patch fixes broken pxaficp-ir. The problem was in incorrect
> net_device_ops being specified which prevented the driver from
> operating. The symptoms were:
> - failing ifconfig for IrLAN, resulting in
> SIOCSIFFLAGS: Cannot assign requested address
> - irattach working for IrCOMM, but the port stayed disabled
>
> Moreover this patch corrects missing sysfs device link.
>
> btw. guys, be honest, when did you last tested pxaficp-ir on real hardware? ;-)
>
Well, this seems to be brought by the net_device_ops change, which seems
to happen silently without any of us being notified.
OK, netdev and Alex are copied, so that we can look into this issue a bit
deeper:
1. it looks to me that SIOCSIFFLAGS actually returned -EADDRNOTAVAIL, which
is likely caused by eth_validate_addr, the default eth_addr comes with
irda should be "00:00:00:00:00:00" if not explicitly specified (kzalloc),
and this should be the problem, solution ? Either give a valid address
to the irda net_device or remove this 'ndo_validate_addr'. And which is
a correct fix will impact on the .ndo_set_mac_address
2. '.ndo_change_mtu' ? It looks to me that Irda device doesn't care too much
about the MTU, eth_change_mtu is supposed to work just fine and not to
cause any side effects, and may just benefit later irda device drivers if
there is a weird device happens to care about MTU
- eric
Marek's original patch in attachment.
[-- Attachment #2: 0001-pxaficp-ir-remove-incorrect-net_device_ops.patch --]
[-- Type: text/x-diff, Size: 1520 bytes --]
>From 28b229f0f3f807d775a7e70b96c018eef935a24a Mon Sep 17 00:00:00 2001
From: Marek Vasut <marek.vasut@gmail.com>
Date: Fri, 24 Jul 2009 02:44:02 +0200
Subject: [PATCH] pxaficp-ir - remove incorrect net_device_ops
This patch fixes broken pxaficp-ir. The problem was in incorrect
net_device_ops being specified which prevented the driver from
operating. The symptoms were:
- failing ifconfig for IrLAN, resulting in
SIOCSIFFLAGS: Cannot assign requested address
- irattach working for IrCOMM, but the port stayed disabled
Moreover this patch corrects missing sysfs device link.
Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
---
drivers/net/irda/pxaficp_ir.c | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/net/irda/pxaficp_ir.c b/drivers/net/irda/pxaficp_ir.c
index 4edbdbe..f5b7d83 100644
--- a/drivers/net/irda/pxaficp_ir.c
+++ b/drivers/net/irda/pxaficp_ir.c
@@ -820,9 +820,6 @@ static const struct net_device_ops pxa_irda_netdev_ops = {
.ndo_stop = pxa_irda_stop,
.ndo_start_xmit = pxa_irda_hard_xmit,
.ndo_do_ioctl = pxa_irda_ioctl,
- .ndo_change_mtu = eth_change_mtu,
- .ndo_validate_addr = eth_validate_addr,
- .ndo_set_mac_address = eth_mac_addr,
};
static int pxa_irda_probe(struct platform_device *pdev)
@@ -847,6 +844,7 @@ static int pxa_irda_probe(struct platform_device *pdev)
if (!dev)
goto err_mem_3;
+ SET_NETDEV_DEV(dev, &pdev->dev);
si = netdev_priv(dev);
si->dev = &pdev->dev;
si->pdata = pdev->dev.platform_data;
--
1.6.3.3
next parent reply other threads:[~2009-07-28 3:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200907240257.10906.marek.vasut@gmail.com>
2009-07-28 3:01 ` Eric Miao [this message]
2009-07-29 11:16 ` [PATCH] pxaficp-ir - remove incorrect net_device_ops Alexander Beregalov
2009-08-05 14:02 ` Marek Vasut
2009-08-21 22:54 ` Marek Vasut
2009-08-21 22:54 ` Marek Vasut
2009-08-23 17:55 ` Alexander Beregalov
2009-08-23 17:55 ` Alexander Beregalov
2009-08-24 1:49 ` David Miller
2009-08-24 1:49 ` David Miller
2009-08-24 4:38 ` Alexander Beregalov
2009-08-24 4:38 ` Alexander Beregalov
2009-08-24 5:57 ` David Miller
2009-08-24 5:57 ` David Miller
2009-08-24 12:47 ` Marek Vasut
2009-08-24 12:47 ` Marek Vasut
2009-07-24 0:44 Marek Vasut
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=4A6E69FA.9010903@gmail.com \
--to=eric.y.miao@gmail.com \
--cc=a.beregalov@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux@arm.linux.org.uk \
--cc=marek.vasut@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=samuel@sortiz.org \
/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.