Alexander Graf writes:
> On 21.11.2010, at 13:37, Blue Swirl wrote:
>
>> On Fri, Nov 19, 2010 at 2:56 AM, Alexander Graf wrote:
>>> So far we have C preprocessor defines for target and host config
>>> options, but we're lacking any information on which devices are
>>> available.
>>>
>>> We do n
On 10.12.2010, at 13:37, Markus Armbruster wrote:
> Alexander Graf writes:
>
>> On 21.11.2010, at 13:37, Blue Swirl wrote:
>>
>>> On Fri, Nov 19, 2010 at 2:56 AM, Alexander Graf wrote:
So far we have C preprocessor defines for target and host config
options, but we're lacking any in
On Sun, Nov 21, 2010 at 12:45 PM, Alexander Graf wrote:
>
> On 21.11.2010, at 13:37, Blue Swirl wrote:
>
>> On Fri, Nov 19, 2010 at 2:56 AM, Alexander Graf wrote:
>>> So far we have C preprocessor defines for target and host config
>>> options, but we're lacking any information on which devices a
On 21.11.2010, at 13:37, Blue Swirl wrote:
> On Fri, Nov 19, 2010 at 2:56 AM, Alexander Graf wrote:
>> So far we have C preprocessor defines for target and host config
>> options, but we're lacking any information on which devices are
>> available.
>>
>> We do need that information at times tho
On Fri, Nov 19, 2010 at 2:56 AM, Alexander Graf wrote:
> So far we have C preprocessor defines for target and host config
> options, but we're lacking any information on which devices are
> available.
>
> We do need that information at times though, for example in the
> ahci patch where we need to
So far we have C preprocessor defines for target and host config
options, but we're lacking any information on which devices are
available.
We do need that information at times though, for example in the
ahci patch where we need to call a legacy init function depending
on whether we have support c
