It seems likely that at some point we will want a generic interrupt uclass.
But this is a big undertaking as it involves unifying code across multiple
architectures.
As a first step, create a simple IRQ uclass and a driver for x86. This can
be generalised later as required.
Adjust pirq_init() to
Hi Bin,
On 14 December 2015 at 22:45, Bin Meng wrote:
> Hi Simon,
>
> On Tue, Dec 15, 2015 at 10:04 AM, Bin Meng wrote:
>> Hi Simon,
>>
>> On Tue, Dec 15, 2015 at 6:14 AM, Simon Glass wrote:
>>> Hi Bin,
>>>
>>> On 13 December 2015 at 23:05, Bin Meng wrote:
Hi Simon,
On Tue, Dec
Hi Simon,
On Tue, Dec 15, 2015 at 10:04 AM, Bin Meng wrote:
> Hi Simon,
>
> On Tue, Dec 15, 2015 at 6:14 AM, Simon Glass wrote:
>> Hi Bin,
>>
>> On 13 December 2015 at 23:05, Bin Meng wrote:
>>> Hi Simon,
>>>
>>> On Tue, Dec 1, 2015 at 12:46 PM, Simon Glass wrote:
It seems likely that at
On Mon, Dec 14, 2015 at 2:05 PM, Bin Meng wrote:
> Hi Simon,
>
> On Tue, Dec 1, 2015 at 12:46 PM, Simon Glass wrote:
>> It seems likely that at some point we will want a generic interrupt uclass.
>> But this is a big undertaking as it involves unifying code across multiple
>> architectures.
>>
>>
Hi Simon,
On Tue, Dec 15, 2015 at 6:14 AM, Simon Glass wrote:
> Hi Bin,
>
> On 13 December 2015 at 23:05, Bin Meng wrote:
>> Hi Simon,
>>
>> On Tue, Dec 1, 2015 at 12:46 PM, Simon Glass wrote:
>>> It seems likely that at some point we will want a generic interrupt uclass.
>>> But this is a big
Hi Bin,
On 13 December 2015 at 23:05, Bin Meng wrote:
> Hi Simon,
>
> On Tue, Dec 1, 2015 at 12:46 PM, Simon Glass wrote:
>> It seems likely that at some point we will want a generic interrupt uclass.
>> But this is a big undertaking as it involves unifying code across multiple
>> architectures.
Hi Simon,
On Tue, Dec 1, 2015 at 12:46 PM, Simon Glass wrote:
> It seems likely that at some point we will want a generic interrupt uclass.
> But this is a big undertaking as it involves unifying code across multiple
> architectures.
>
> As a first step, create a simple IRQ uclass and a driver fo
It seems likely that at some point we will want a generic interrupt uclass.
But this is a big undertaking as it involves unifying code across multiple
architectures.
As a first step, create a simple IRQ uclass and a driver for x86. This can
be generalised later as required.
Adjust pirq_init() to
8 matches
Mail list logo