All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Pont <andy.pont@sdcsystems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Quark compile errors
Date: Wed, 20 May 2015 16:11:16 +0100	[thread overview]
Message-ID: <00fe01d0930f$3dfbd090$b9f371b0$@pont@sdcsystems.com> (raw)
In-Reply-To: <CAEUhbmVoi7KWU8uK+46CKAr=bsFxB_=i8S=q6ODL_ubLra9kLQ@mail.gmail.com>

Hi Bin,

> BTW, so you are working on this board?
> http://www.siliconmotion.com/EW_Pages/Osprey.html
> Looks like a quark based board with graphics support! Are you planning
> to submit patches to enable it?

It is indeed for one of those boards, as an off-radar task to get my head back into x86 after lots of time spent playing with ARM!

At the moment I am still waiting for some physical hardware but once I have some and have tested everything then yes, I will submit the patches for it.

Regards,

Andy.

  reply	other threads:[~2015-05-20 15:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <555c5b41.d1cf2a0a.643b.4893SMTPIN_ADDED_BROKEN@mx.google.com>
2015-05-20 10:12 ` [U-Boot] Quark compile errors Bin Meng
2015-05-20 10:20   ` Andy Pont
     [not found]   ` <555c6006.91196b0a.78ce.ffffce95SMTPIN_ADDED_BROKEN@mx.google.com>
2015-05-20 14:31     ` Simon Glass
2015-05-20 14:43       ` Andy Pont
     [not found]   ` <555c6006.913a2a0a.2890.ffffd8b9SMTPIN_ADDED_BROKEN@mx.google.com>
2015-05-20 14:44     ` Bin Meng
2015-05-20 14:50       ` Andy Pont
     [not found]       ` <555c9f2c.488a320a.08da.08a8SMTPIN_ADDED_BROKEN@mx.google.com>
2015-05-20 14:53         ` Bin Meng
2015-05-20 14:58           ` Andy Pont
     [not found]           ` <555ca13c.c3046b0a.6987.fffff1e3SMTPIN_ADDED_BROKEN@mx.google.com>
2015-05-20 15:07             ` Bin Meng
2015-05-20 15:11               ` Andy Pont [this message]
2015-05-20 10:00 Andy Pont

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='00fe01d0930f$3dfbd090$b9f371b0$@pont@sdcsystems.com' \
    --to=andy.pont@sdcsystems.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.