Hi,
thanks to Marc Jones' SGD patch for the Auron board
(f3214d02482a4104d7276f06d6b326b2a54c4262), I was able to get my
Auron_Paine up to ramstage.
Unfortunately, the IGD code in soc/intel/broadwell/ appears to be
somewhat broken. Based off Aaron's guidance on IRC, I've pin-pointed the
issue to
oh, I thought you'd say +1^2 :)
--vb
On Mon, Oct 19, 2015 at 1:05 PM, ron minnich wrote:
> I won't say +1, that's so 2014.
>
> Plus Two!
>
> ron
>
> On Mon, Oct 19, 2015 at 11:53 AM Peter Stuge wrote:
>>
>> Patrick Georgi wrote:
>> > The paragraph in
I won't say +1, that's so 2014.
Plus Two!
ron
On Mon, Oct 19, 2015 at 11:53 AM Peter Stuge wrote:
> Patrick Georgi wrote:
> > The paragraph in question is:
> >
> > You should have received a copy of the GNU General Public License
> > along with this program; if not, write
* Mario Goljak [150925 16:06]:
> Hi guys,
>
> I just came across thinkpad forum thread where people are discuss about
> hardware mods for getting FHD screen on lenovo x220/x230 laptops.
> http://forum.thinkpads.com/viewtopic.php?f=43=106919=90
>
> What do you guys think, will
Hi all,
we recently removed the FSF addresses from license headers in our
files to avoid the maintenance of updating them every time the FSF
decides to move their office.
Now we also added checkpatch.pl that comes from Linux to automatically
ensure some consistency across the tree, and it looks
Patrick Georgi wrote:
> The paragraph in question is:
>
> You should have received a copy of the GNU General Public License
> along with this program; if not, write to the Free Software
> Foundation, Inc.
>
>
> Since the GPL is fairly well-known (incl where to find it), and our
> tree
* Georg Wicherski [151019 17:39]:
> Hi,
>
> thanks to Marc Jones' SGD patch for the Auron board
> (f3214d02482a4104d7276f06d6b326b2a54c4262), I was able to get my
> Auron_Paine up to ramstage.
>
> Unfortunately, the IGD code in soc/intel/broadwell/ appears to be
> somewhat
> is there anyway to dynamic define std to gnu99 when detect build with cygwin?
cbfstool is already defining -std=c99. I don't see a strong reason why
we shouldn't just change that to gnu99 globally.
>>> 2. default build will error as below,
>>> HOSTCC cbfstool/cbfstool.o
>>>
On 10/19/2015 11:44 AM, Patrick Georgi wrote:
> Hi all,
>
> we recently removed the FSF addresses from license headers in our
> files to avoid the maintenance of updating them every time the FSF
> decides to move their office.
+2
> Now we also added checkpatch.pl that comes from Linux to
I think switching to c99 per default is a great idea. The problem below should
be fixed by http://review.coreboot.org/#/c/11666/ and the following patch.
Stefan
On Oct 19, 2015, Julius Werner wrote:
>> is there anyway to dynamic define std to gnu99 when detect build with
10 matches
Mail list logo