Re: com(4) and LSI bug workaround

[KIYOHARA Takashi <kiyohara%kk.iij4u.or.jp@localhost>]

Hi!

From: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
Date: Tue, 1 Oct 2013 21:19:01 +0900

> First of all, your guess has no evidence and actually it seems incorrect.
> 
> There are some articles that indicate it's a documented future:
> http://permalink.gmane.org/gmane.linux.ports.arm.kernel/203948

Yes.
Although that those are not the things for 16750 understood me, I did
not know that it was IP of Synopsys DesignWare.  And although his mail
does not have a corroboration which is a fact, either, probably it is
right.


> Isn't it much simpler and explicit to call such a MD workaround
> function directly from comintr() and wrap those blocks with
> #if COM_XXXMDname > 0 / #endif with "needs-flag" declaration
> in the config(9) file?

I think that I should check not by "needs-flag" but by COM_TYPE_XXXX.
Since ARMADAXP has some PCIe, com should be able to be attached there.

  COM_TYPE_APBUART or COM_TYPE_SNPS or ... ?


Thanks,
--
kiyohara