Hi Wolfgang,

I could confirm below.
With FIFO mode, it is able to receive packet with in-order.
We are now implementing FIFO mode.

Thanks, Ohtake(OKISemi)

----- Original Message ----- 
From: "Wolfgang Grandegger" <redacted>
To: "Masayuki Ohtake" <masa-korg-ECg8zkTtlr0C6LszWs/t0g@public.gmane.org>
Cc: <redacted>; <redacted>; <redacted>; <redacted>;
[off-list ref]; [off-list ref]; [off-list ref]; [off-list ref];
"Christian Pellegrin" [off-list ref]; "Tomoya MORINAGA" [off-list ref]; [off-list ref];
"David S. Miller" [off-list ref]; [off-list ref]; "Samuel Ortiz" [off-list ref]
Sent: Friday, October 01, 2010 9:40 PM
Subject: Re: [MeeGo-Dev][PATCH v3] Topcliff: Update PCH_CAN driver to 2.6.35

On 10/01/2010 12:02 PM, Masayuki Ohtake wrote:

quoted

Hi Wolfgang Grandegger,

Thank you for your comments.

We will modify and re-post ASAP.

I have a comment about below.

quoted

In this driver you are using just *one* RX object. This means that the
CPU must handle new messages as quickly as possible otherwise message
losses will happen, right?. For sure, this will not make user's happy.
Any chance to use more RX objects in FIFO mode?

In case implementing with FIFO mode,
received packets may be our of order.

Hm, FIFO means "First in First out"! It might be tricky to implement,
though.

quoted

Because our CAN register access is slow.

I am confirming our CAN HW spec and the possibility of our-of-order.

I don't understand?

Wolfgang.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html