From: Alexandre Belloni <alexandre.belloni@free-electrons.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: Wed, 17 Feb 2016 23:59:43 +0100 [thread overview]
Message-ID: <20160217225943.GO2189@piout.net> (raw)
In-Reply-To: <n9vrbm$b0a$1@ger.gmane.org>
Hi,
On 16/02/2016 at 18:55:50 +0000, Grant Edwards wrote :
> 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.
>
The best way to contact kernel developers is to use the kernel mailing
lists. For AT91, this is the linux arm kernel mailing list (lakml):
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-02-17 22:59 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
2016-02-17 22:59 ` Alexandre Belloni [this message]
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=20160217225943.GO2189@piout.net \
--to=alexandre.belloni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox