From: Philippe De Muyter <phdm@macqel.be>
To: chas@cmf.nrl.navy.mil, netdev@vger.kernel.org
Subject: [PATCH] atm : fix /sys/devices/virtual/atm/X/carrier(ATM_PHY_SIG_UNKNOWN)
Date: Sat, 13 Feb 2010 22:56:33 +0100 [thread overview]
Message-ID: <20100213215633.GA4345@frolo.macqel> (raw)
When trying to design udev rules to automate usage of cxacru usb atm (adsl)
modem, I have discovered that /sys/devices/virtual/atm/cxacru0/carrier had the
value '1' while actually carrier was not yet established and real carrier
state was not yet known to linux. I propose to fix that by using '?' as the
/sys/devices/virtual/atm/cxacru0/carrier value when carrier state is not yet
known to linux. Any other value except '1' would also be OK for me.
--
Currently, just after the interface creation,
/sys/devices/virtual/atm/cxacru0/carrier gives wrong info (carrier = 1),
while actually carrier is unknown. Fix that.
Signed-off-by: Philippe De Muyter <phdm@macqel.be>
--- a/net/atm/atm_sysfs.c 2010-02-13 22:54:04.598847195 +0100
+++ b/net/atm/atm_sysfs.c 2010-02-13 19:13:45.395308531 +0100
@@ -63,9 +63,9 @@ static ssize_t show_carrier(struct devic
char *pos = buf;
struct atm_dev *adev = to_atm_dev(cdev);
- pos += sprintf(pos, "%d\n",
- adev->signal ==
- adev->signal == ATM_PHY_SIG_LOST ? 0 : 1);
+ pos += sprintf(pos, "%c\n",
+ adev->signal == ATM_PHY_SIG_FOUND ? '1' :
+ adev->signal == ATM_PHY_SIG_LOST ? '0' : '?');
return pos - buf;
}
next reply other threads:[~2010-02-13 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 21:56 Philippe De Muyter [this message]
2010-02-13 23:24 ` [PATCH] atm : fix /sys/devices/virtual/atm/X/carrier(ATM_PHY_SIG_UNKNOWN) Chas Williams (CONTRACTOR)
2010-02-14 17:51 ` Philippe De Muyter
2010-02-14 21:34 ` Chas Williams (CONTRACTOR)
2010-02-17 6:16 ` David Miller
2010-02-17 11:35 ` Philippe De Muyter
2010-02-18 14:22 ` Chas Williams (CONTRACTOR)
2013-08-08 8:34 ` Philippe De Muyter
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=20100213215633.GA4345@frolo.macqel \
--to=phdm@macqel.be \
--cc=chas@cmf.nrl.navy.mil \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox