From: Srinivas rao <ch_srinivas321@yahoo.co.in>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos <ecos-discuss@sourceware.org>
Subject: Re: [ECOS] Operation timed out
Date: Tue, 06 Mar 2007 10:08:00 -0000 [thread overview]
Message-ID: <112422.68681.qm@web7904.mail.in.yahoo.com> (raw)
Iam reading the MAC ID from EEPROM of The Chip and same Mac Id I programmed into the chip using below code of rltk8139 driver(if_8139.c)
if (enaddr != NULL) {
for (i = 0; i < 6; ++i) {
rltk8139_info->mac[i] = enaddr[i];
OUTB(enaddr[i], rltk8139_info->base_address + IDR0 + i);
}
}
After this code I reading the MAC Id using below code and Its giving same MAC Id.
for (i = 0; i < 6; ++i)
{
rltk8139_info->mac[i] = INB(rltk8139_info->base_address + IDR0 + i);
diag_printf("%x:",rltk8139_info->mac[i]);
}
In MAC Id I didn't find any chanage.
Srinivas Rao.Ch
----- Original Message ----
From: Srinivas rao <ch_srinivas321@yahoo.co.in>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos <ecos-discuss@sourceware.org>
Sent: Tuesday, 6 March, 2007 2:14:03 PM
Subject: Re: [ECOS] Operation timed out
Sorry! for the late response
Iam not reading and programming the MAC id from EEPROM.
Iam not receving the broadcast packets also.
Srinivas Rao.Ch
----- Original Message ----
From: Andrew Lunn <andrew@lunn.ch>
To: Srinivas rao <ch_srinivas321@yahoo.co.in>
Cc: ecos <ecos-discuss@sourceware.org>
Sent: Thursday, 15 February, 2007 6:40:26 PM
Subject: Re: [ECOS] Operation timed out
On Thu, Feb 15, 2007 at 03:59:24PM +0530, Srinivas rao wrote:
> Hi,
>
> Iam using rltk 8139 pci card and eCos rltk 8139 eternet drinver for
> my NUPort Board
> Iam testing the ping_test case on my NUPort Board.
> the request packets are sending but reply packets are not recieving,
> I checked in the Ehtereal.
Another thing to check is if the device knows its own MAC
addresses. Sometimes you need to read if from an EEPROM and program it
into the chip. Check if you receive Ethernet broadcast packets, but
not unicast packets addressed to the device.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
__________________________________________________________
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2007-03-06 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 10:08 Srinivas rao [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-06 8:44 Srinivas rao
2007-02-15 10:29 Srinivas rao
2007-02-15 11:23 ` Nick Garnett
2007-02-15 13:10 ` Andrew Lunn
2007-02-15 13:16 ` Gary Thomas
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=112422.68681.qm@web7904.mail.in.yahoo.com \
--to=ch_srinivas321@yahoo.co.in \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).