All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8576] Building embedded Linux for Atmel SAMA5D4_Xplained with HDMI work not propber. HDMI does not work
Date: Tue, 16 Feb 2016 18:55:50 +0000 (UTC)	[thread overview]
Message-ID: <n9vrbm$b0a$1@ger.gmane.org> (raw)
In-Reply-To: bug-8576-163-X6I9k76wUk@https.bugs.busybox.net/

On 2016-02-16, bugzilla at busybox.net <bugzilla@busybox.net> wrote:

> --- Comment #3 from JensAmberg <JensAmberg@mail.de> ---
> How can i contact Atmel Kernel developer? I post an bug on www.linux4sam.com
> Forum. But nothing happens

I've never had any luck all with linux4sam.com, and have given up
using it.  Questions are usually completely ignored.  If there are any
responses, they're usually way off base. You might as well walk down
the street and ask panhandlers: it appears to be the clueless leading
the incompetent.  You might try contacting your Atmel FAE to see if he
can help.  There also used to be one or two knowlegable Atmel
employees who participated in comp.arch.embedded, but that was several
years ago.

-- 
Grant Edwards               grant.b.edwards        Yow! Used staples are good
                                  at               with SOY SAUCE!
                              gmail.com            

  reply	other threads:[~2016-02-16 18:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31 21:30 [Buildroot] [Bug 8576] New: Building embedded Linux for Atmel SAMA5D4_Xplained with HDMI work not propber. HDMI does not work bugzilla at busybox.net
2016-01-25 19:10 ` [Buildroot] [Bug 8576] " bugzilla at busybox.net
2016-02-14 21:08 ` bugzilla at busybox.net
2016-02-16 17:54 ` bugzilla at busybox.net
2016-02-16 18:55   ` Grant Edwards [this message]
2016-02-17 22:59     ` Alexandre Belloni

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='n9vrbm$b0a$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=buildroot@busybox.net \
    /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.