From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [E1000-devel] ARM support for igb driver
Date: Tue, 03 Jun 2014 15:57:18 +0100 [thread overview]
Message-ID: <538DE24E.10904@codethink.co.uk> (raw)
In-Reply-To: <5368F898.2000803@intel.com>
On 06/05/14 15:58, Alexander Duyck wrote:
> Shiv,
>
> I think we are at the limits of what we can do from the Intel end.
> Based on the comments from Thomas it sounds like there shouldn't be any
> issues specifically with ARM that prevent the use of IGB PCIe devices,
> and the fact is the error your are seeing "Unhandled fault: imprecise
> external abort (0x1406) at 0x00000000" can indicate some sort of bus
> fault. It would probably be best to work with someone more familiar
> with the inner workings of ARM CPUs as they might be able to work out
> some other workarounds for the external abort.
I did send a pair of patches for this, as imprecise aborts are not
traceable to their source instruction and there is a case that it
should not abort any tasks.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2014-06-03 14:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHH3p5KAwyMOY=ai_h0eM+JwYLtTO8d4jVaVOWVtOakhqPRTew@mail.gmail.com>
[not found] ` <CF7EA37A.4676A%matthew.vick@intel.com>
[not found] ` <CAHH3p5JFc3jgeK7OFd1rtgDS3gjRdjiPr3LwwqfyKMPGSTwMWA@mail.gmail.com>
[not found] ` <CF7FD060.46A87%matthew.vick@intel.com>
[not found] ` <CAHH3p5J8V6uWEzbCoT+x-6_2x1q=nc=_oMn0qnnj113FmeuW6A@mail.gmail.com>
[not found] ` <9B4A1B1917080E46B64F07F2989DADD6533627A5@ORSMSX114.amr.corp.intel.com>
[not found] ` <CAHH3p5KEPXw5mxP-13evd774nyO5C13ky0=fCaZPCNVx1gh3Ow@mail.gmail.com>
[not found] ` <CAHH3p5LaRwgdECxsO4OZSdWEhGt232yj-3347kYEStP6NLg2xg@mail.gmail.com>
[not found] ` <5360041A.7030005@intel.com>
[not found] ` <CAHH3p5L6WM3FaZ19Tw9vUcsk+kERfBKnGC2BRtnftJR1pbSF7g@mail.gmail.com>
2014-05-05 15:28 ` [E1000-devel] ARM support for igb driver Alexander Duyck
[not found] ` <CAHH3p5KEbvziVxg-9o45-chp=6U2JnW=ffk1p85GKFyWXiX8CQ@mail.gmail.com>
2014-05-05 20:00 ` Alexander Duyck
2014-05-05 20:38 ` Thomas Petazzoni
2014-05-05 21:20 ` Alexander Duyck
[not found] ` <CAHH3p5L4DaORYJ8_6zMEY3ikEnABU1L0B2C6Fezb_g6dCjtr5Q@mail.gmail.com>
2014-05-06 14:58 ` Alexander Duyck
2014-06-03 14:57 ` Ben Dooks [this message]
2014-05-06 15:18 ` Arnd Bergmann
2014-05-06 15:24 ` Lucas Stach
2014-05-06 15:33 ` Arnd Bergmann
2014-05-30 11:50 ` shiv prakash Agarwal
2014-05-30 17:21 ` Alexander Duyck
2014-05-30 18:02 ` shiv prakash Agarwal
2014-05-30 19:18 ` Jason Gunthorpe
2014-05-30 19:35 ` shiv prakash Agarwal
2014-05-30 19:56 ` Arnd Bergmann
2014-05-30 20:14 ` shiv prakash Agarwal
2014-05-30 21:11 ` Fujinaka, Todd
2014-05-31 18:34 ` Arnd Bergmann
2014-06-01 5:56 ` shiv prakash Agarwal
2014-06-01 11:46 ` Arnd Bergmann
2014-06-02 4:53 ` shiv prakash Agarwal
2014-06-02 16:05 ` Fujinaka, Todd
2014-06-03 12:33 ` shiv prakash Agarwal
2014-06-03 14:49 ` Ben Dooks
2014-06-03 15:05 ` Arnd Bergmann
2014-06-03 15:13 ` Ben Dooks
2014-06-03 15:23 ` Arnd Bergmann
2014-06-03 15:31 ` Ben Dooks
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=538DE24E.10904@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=linux-arm-kernel@lists.infradead.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).