On Tue, May 2, 2017 at 10:30 AM Arthur Heymans wrote:
> Ok thanks for clarifying.
>
> Aaron Durbin writes:
>
> > On Tue, May 2, 2017 at 5:24 AM, Arthur Heymans
> wrote:
> >> Hi
> >>
> >> I am wondering why newer intel code is being
Ok thanks for clarifying.
Aaron Durbin writes:
> On Tue, May 2, 2017 at 5:24 AM, Arthur Heymans wrote:
>> Hi
>>
>> I am wondering why newer intel code is being pushed to src/soc/intel/*/
>> instead of the traditional
On Tue, May 2, 2017 at 5:24 AM, Arthur Heymans wrote:
> Hi
>
> I am wondering why newer intel code is being pushed to src/soc/intel/*/
> instead of the traditional src/{cpu,southbridge,northbridge}/intel ?
The era of mix and match ICs is pretty much gone. Even when there are
Hi
I am wondering why newer intel code is being pushed to src/soc/intel/*/
instead of the traditional src/{cpu,southbridge,northbridge}/intel ?
I know that physically things are now on one chip hence the soc but the
code itself is often very similar to older cpu/southbridge/northbridge
code. A
4 matches
Mail list logo