qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Jason Wang <jasowang@redhat.com>,
	Laurent Vivier <laurent@vivier.eu>,
	"qemu-stable@nongnu.org" <qemu-stable@nongnu.org>,
	Herve Poussineau <hpoussin@reactos.org>,
	Aleksandar Rikalo <aleksandar.rikalo@rt-rk.com>
Subject: Re: [PATCH 00/10] Fixes for DP8393X SONIC device emulation
Date: Sat, 21 Dec 2019 13:03:49 +0100	[thread overview]
Message-ID: <CAL1e-=iz8VDjYkObcsid6eKimH+a62Ttk5f+=2xoFGVgpg-EdQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.21.1.1912210941150.53@nippy.intranet>

[-- Attachment #1: Type: text/plain, Size: 1876 bytes --]

On Saturday, December 21, 2019, Finn Thain <fthain@telegraphics.com.au>
wrote:

> On Fri, 20 Dec 2019, Laurent Vivier wrote:
>
> > Le 20/12/2019 ? 12:38, Aleksandar Markovic a ?crit?:
> > > On Sat, Dec 14, 2019 at 2:29 AM Finn Thain <fthain@telegraphics.com.au>
> wrote:
> > >>
> > >> Hi All,
> > >>
> > >> There is a bug in the DP8393X emulation that can stop packet
> reception.
> > >>
> > >> Whilst debugging that issue I found that the receiver algorithm
> differs
> > >> from the one described in the National Semiconductor datasheet.
> > >>
> > >
> > > Finn, could you please provide the link to the exact datasheet that
> > > you used for reference, so that we are on the same page while looking
> > > at your code?
> >
> > According to his comments ,"National Semiconductor DP83932C" and
> > sections seem to be the same, I think the datasheet is:
> >
> > https://www.eit.lth.se/fileadmin/eit/courses/datablad/Periphery/
> Communication/DP83932C.pdf
> >
>
> Yes. I know of 3 datasheets from National Semiconductor,
>
> 11719  DP83934CVUL-20/25 MHz SONIC-T Systems-Oriented Network Interface
> Controller with Twisted Pair Interface
> 10492  DP83932C-20/25/33 MHz SONIC Systems-Oriented Network Interface
> Controller
> 11722  DP83916 SONIC-16 Systems-Oriented Network Interface Controller
>
> The publication numbered 10492 is the one that Laurent linked to. It and
> 11722 both have the same table of contents. The references I gave in the
> patch descriptions are applicable to these. (Having said that, I see now
> that I did mess up one reference. I'll fix it.)
>
> The "1995 National Ethernet Databook" on bitsavers has more information.
> https://mirrorservice.org/sites/www.bitsavers.org/components/national/_
> dataBooks/1995_National_Ethernet_Databook.pdf
>
> --


Finn,

I truly appreciate your detailed response.

Aleksandar


> > Thanks,
> > Laurent
> >
>

[-- Attachment #2: Type: text/html, Size: 2908 bytes --]

      reply	other threads:[~2019-12-21 12:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-14  1:25 [PATCH 00/10] Fixes for DP8393X SONIC device emulation Finn Thain
2019-12-14  1:25 ` [PATCH 08/10] dp8393x: Implement packet size limit and RBAE interrupt Finn Thain
2019-12-14  1:25 ` [PATCH 09/10] dp8393x: Don't stop reception upon RBE interrupt assertion Finn Thain
2019-12-14  1:25 ` [PATCH 06/10] dp8393x: Clear RRRA command register bit only when appropriate Finn Thain
2019-12-14 13:31   ` Philippe Mathieu-Daudé
2019-12-14  1:25 ` [PATCH 02/10] dp8393x: Clean up endianness hacks Finn Thain
2019-12-14  1:25 ` [PATCH 05/10] dp8393x: Update LLFA register Finn Thain
2019-12-14  1:25 ` [PATCH 10/10] dp8393x: Don't clobber packet checksum Finn Thain
2019-12-14 13:21   ` Philippe Mathieu-Daudé
2019-12-14  1:25 ` [PATCH 07/10] dp8393x: Implement TBWC0 and TBWC1 registers to restore buffer state Finn Thain
2019-12-14  1:25 ` [PATCH 01/10] dp8393x: Mask EOL bit from descriptor addresses Finn Thain
2019-12-14 13:35   ` Philippe Mathieu-Daudé
2019-12-14 23:21     ` Finn Thain
2019-12-14  1:25 ` [PATCH 04/10] dp8393x: Don't advance RX descriptor twice Finn Thain
2019-12-14  1:25 ` [PATCH 03/10] dp8393x: Have dp8393x_receive() return the packet size Finn Thain
2019-12-14 13:26   ` Philippe Mathieu-Daudé
2019-12-14  1:43 ` [PATCH 00/10] Fixes for DP8393X SONIC device emulation no-reply
2019-12-14  2:52   ` Finn Thain
2019-12-14 13:38     ` Philippe Mathieu-Daudé
2019-12-14 13:45       ` Eric Blake
2019-12-14 17:17 ` Aleksandar Markovic
2019-12-14 23:16   ` Finn Thain
2019-12-14 23:32     ` Aleksandar Markovic
2019-12-14 23:35       ` Aleksandar Markovic
2019-12-20  4:24         ` Finn Thain
2019-12-23 17:17           ` Philippe Mathieu-Daudé
2019-12-24  0:12             ` NetBSD/arc on MIPS Magnum, was " Finn Thain
2019-12-24  4:33               ` Finn Thain
2019-12-24  6:53                 ` Hervé Poussineau
2020-01-06 22:15                   ` Finn Thain
2019-12-16  0:36     ` Finn Thain
2019-12-20  4:21       ` Finn Thain
2019-12-20 11:38 ` Aleksandar Markovic
2019-12-20 12:03   ` Aleksandar Markovic
2019-12-20 12:54   ` Laurent Vivier
2019-12-20 23:22     ` Finn Thain
2019-12-21 12:03       ` Aleksandar Markovic [this message]

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='CAL1e-=iz8VDjYkObcsid6eKimH+a62Ttk5f+=2xoFGVgpg-EdQ@mail.gmail.com' \
    --to=aleksandar.m.mail@gmail.com \
    --cc=aleksandar.rikalo@rt-rk.com \
    --cc=fthain@telegraphics.com.au \
    --cc=hpoussin@reactos.org \
    --cc=jasowang@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).