From: Antony T Curtis <antony.t.curtis@ntlworld.com>
To: Karel Gardas <kgardas@objectsecurity.com>
Cc: QEMU Development Mailing List <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Updated 3c509 NIC patch.
Date: Thu, 20 Jan 2005 21:21:01 +0000 [thread overview]
Message-ID: <1106256061.75381.29.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <Pine.LNX.4.43.0501202106550.806-100000@thinkpad.gardas.net>
On Thu, 2005-01-20 at 21:15 +0100, Karel Gardas wrote:
> On Thu, 20 Jan 2005, Karel Gardas wrote:
>
> > > I would say that your safest and most easiest way forward is to use the
> > > 3c509 in it's "powered on" configuration, and set the RTEMS driver to
> > > use it at that IO/IRQ without the automagic probe.
> >
> > I will certainly give it a try.
>
> Well, it seems I've got things to the shape when initialization and driver
> attaching goes well and RTEMS seems to got it.
> Unfortunatelly, when trying to open connection from host to guest while
> using proper user-net command-line parameters, I see this debug output
> comming from Qemu:
>
> tcm509_receive: size=58
> packet dhost=00:00:00:00:00:00, padr=21:03:76:12:09:75
> padr_match result=0 (rx_filter=0x0007)
>
> That's just snipped from more such lines, basically they just repeat.
You have the debug code enabled. You should undef TCM_DEBUG
Are you able to set an IP address and get it talking?
<snip>
> From looking into the source code, it seems dhost is destination host
> ethernet address and I just wonder why is it set to zeros when it should
> be 21:03:76:12:09:75. Do you think I should blame my changes or better
> overlooking of some places where I should setup ethernet address in the
> RTEMS driver, or is this just another issue with your 3c509 emulation?
>
> Thanks,
> Karel
> --
> Karel Gardas kgardas@objectsecurity.com
> ObjectSecurity Ltd. http://www.objectsecurity.com
>
--
Antony T Curtis, BSc. UNIX, Linux, *BSD, Networking
antony.t.curtis@ntlworld.com C++, J2EE, Perl, MySQL, Apache
IT Consultancy.
next prev parent reply other threads:[~2005-01-20 22:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.43.0501201031360.806-100000@thinkpad.gardas.net>
2005-01-20 12:17 ` [Qemu-devel] Updated 3c509 NIC patch Antony T Curtis
2005-01-20 15:07 ` Karel Gardas
2005-01-20 16:56 ` Antony T Curtis
2005-01-20 17:13 ` Karel Gardas
2005-01-20 20:15 ` Karel Gardas
2005-01-20 21:21 ` Antony T Curtis [this message]
2005-01-20 21:54 ` Karel Gardas
2005-01-19 10:51 Karel Gardas
2005-01-19 13:09 ` Antony T Curtis
2005-01-19 17:28 ` Antony T Curtis
2005-01-19 18:59 ` Karel Gardas
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=1106256061.75381.29.camel@pcgem.rdg.cyberkinetica.com \
--to=antony.t.curtis@ntlworld.com \
--cc=kgardas@objectsecurity.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).