On 05/22/14 15:05, Christopher Covington wrote:
> Hi Stephen,
>
> On 10/18/2013 02:34 PM, Stephen Boyd wrote:
>> On 10/18/13 11:14, Christopher Covington wrote:
>>> Put architecture-specific assembly code where it belongs,
>>> allowing for support of additional architectures such as arm64 in
>>> th
Hi Kumar,
On 10/23/2013 01:59 AM, Kumar Gala wrote:
>
> On Oct 18, 2013, at 1:14 PM, Christopher Covington wrote:
>
>> Put architecture-specific assembly code where it belongs,
>> allowing for support of additional architectures such as arm64 in
>> the future.
>>
>> Signed-off-by: Christopher Co
Hi Stephen,
On 10/18/2013 02:34 PM, Stephen Boyd wrote:
> On 10/18/13 11:14, Christopher Covington wrote:
>> Put architecture-specific assembly code where it belongs,
>> allowing for support of additional architectures such as arm64 in
>> the future.
>
> Do you have that patch too? There was also
On Oct 18, 2013, at 1:14 PM, Christopher Covington wrote:
> Put architecture-specific assembly code where it belongs,
> allowing for support of additional architectures such as arm64 in
> the future.
>
> Signed-off-by: Christopher Covington
> ---
> arch/arm/include/asm/dcc.h | 45 ++
On 10/18/13 11:14, Christopher Covington wrote:
> Put architecture-specific assembly code where it belongs,
> allowing for support of additional architectures such as arm64 in
> the future.
Do you have that patch too? There was also a patch a year ago to add
armv5/v4 support to this driver. Maybe
Put architecture-specific assembly code where it belongs,
allowing for support of additional architectures such as arm64 in
the future.
Signed-off-by: Christopher Covington
---
arch/arm/include/asm/dcc.h | 45 +++
drivers/tty/hvc/hvc_dcc.c | 48 ++
6 matches
Mail list logo
