From: moinejf@free.fr (Jean-Francois Moine)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: mvebu: add ethernet to the cm-a510 board
Date: Fri, 6 Feb 2015 08:58:55 +0100 [thread overview]
Message-ID: <20150206085855.7b8d494b@armhf> (raw)
In-Reply-To: <54D3EB26.9020909@gmail.com>
On Thu, 05 Feb 2015 23:13:58 +0100
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> > At this moment, I am trying to configure the framebuffer, but as Moine
> > told me,it seems there is not video driver support for this board in
> > DT... :( .
>
> Not quite true. Video is made up of at least 4 different devices:
> Framebuffer, GPU, Decode engine, and usually DVI/HDMI transmitter or
> VGA.
>
> We do have a driver for the framebuffer (armada_drm) and there is great
> work from Russell King and others on the GPU and Decode engine (IIRC).
Yes, but it has no DT support. Mine has.
> If you are using the sb-a510, I can see from the manual, that DVI
> transmitter is SIL164.. AFAIS there is a driver for it, that maybe
> needs some polishing. Nobody ever tested VGA, but it shouldn't be too
> hard to add support for it as it is directly supported by the
> framebuffer HW.
This asks for some VGA encoder/connector module.
Actually, as Gabriel told me that his screen is directly connected to
the RGB LCD output, I wrote a simple panel for him. This module just
gets the display timings from the DT.
> One quite important driver at least for Dove is a clock source for
> video. Internal clock generators for video are way to limited with
> respect to frequencies to allow any useful resolution.
>From my previous tests with the si5351 in the Cubox, most video modes
should work without external clocks.
> I'll see if I can have a look at the dts stuff this weekend.. that
> way we'll have at least the basic done before moving to the other
> devices.
--
Ken ar c'henta? | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Francois Moine <moinejf-GANU6spQydw@public.gmane.org>
To: Sebastian Hesselbarth
<sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Gabriel Dobato <dobatog-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Russell King - ARM Linux
<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Jason Cooper <jason-NLaQJdtUoK4Be96aLqz0jA@public.gmane.org>,
Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
Gregory Clement
<gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Subject: Re: [PATCH] ARM: dts: mvebu: add ethernet to the cm-a510 board
Date: Fri, 6 Feb 2015 08:58:55 +0100 [thread overview]
Message-ID: <20150206085855.7b8d494b@armhf> (raw)
In-Reply-To: <54D3EB26.9020909-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Thu, 05 Feb 2015 23:13:58 +0100
Sebastian Hesselbarth <sebastian.hesselbarth-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > At this moment, I am trying to configure the framebuffer, but as Moine
> > told me,it seems there is not video driver support for this board in
> > DT... :( .
>
> Not quite true. Video is made up of at least 4 different devices:
> Framebuffer, GPU, Decode engine, and usually DVI/HDMI transmitter or
> VGA.
>
> We do have a driver for the framebuffer (armada_drm) and there is great
> work from Russell King and others on the GPU and Decode engine (IIRC).
Yes, but it has no DT support. Mine has.
> If you are using the sb-a510, I can see from the manual, that DVI
> transmitter is SIL164.. AFAIS there is a driver for it, that maybe
> needs some polishing. Nobody ever tested VGA, but it shouldn't be too
> hard to add support for it as it is directly supported by the
> framebuffer HW.
This asks for some VGA encoder/connector module.
Actually, as Gabriel told me that his screen is directly connected to
the RGB LCD output, I wrote a simple panel for him. This module just
gets the display timings from the DT.
> One quite important driver at least for Dove is a clock source for
> video. Internal clock generators for video are way to limited with
> respect to frequencies to allow any useful resolution.
From my previous tests with the si5351 in the Cubox, most video modes
should work without external clocks.
> I'll see if I can have a look at the dts stuff this weekend.. that
> way we'll have at least the basic done before moving to the other
> devices.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Francois Moine <moinejf@free.fr>
To: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Cc: Gabriel Dobato <dobatog@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@free-electrons.com>
Subject: Re: [PATCH] ARM: dts: mvebu: add ethernet to the cm-a510 board
Date: Fri, 6 Feb 2015 08:58:55 +0100 [thread overview]
Message-ID: <20150206085855.7b8d494b@armhf> (raw)
In-Reply-To: <54D3EB26.9020909@gmail.com>
On Thu, 05 Feb 2015 23:13:58 +0100
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
> > At this moment, I am trying to configure the framebuffer, but as Moine
> > told me,it seems there is not video driver support for this board in
> > DT... :( .
>
> Not quite true. Video is made up of at least 4 different devices:
> Framebuffer, GPU, Decode engine, and usually DVI/HDMI transmitter or
> VGA.
>
> We do have a driver for the framebuffer (armada_drm) and there is great
> work from Russell King and others on the GPU and Decode engine (IIRC).
Yes, but it has no DT support. Mine has.
> If you are using the sb-a510, I can see from the manual, that DVI
> transmitter is SIL164.. AFAIS there is a driver for it, that maybe
> needs some polishing. Nobody ever tested VGA, but it shouldn't be too
> hard to add support for it as it is directly supported by the
> framebuffer HW.
This asks for some VGA encoder/connector module.
Actually, as Gabriel told me that his screen is directly connected to
the RGB LCD output, I wrote a simple panel for him. This module just
gets the display timings from the DT.
> One quite important driver at least for Dove is a clock source for
> video. Internal clock generators for video are way to limited with
> respect to frequencies to allow any useful resolution.
>From my previous tests with the si5351 in the Cubox, most video modes
should work without external clocks.
> I'll see if I can have a look at the dts stuff this weekend.. that
> way we'll have at least the basic done before moving to the other
> devices.
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2015-02-06 7:58 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1YH5bU-0005mG-3L@bombadil.infradead.org>
2015-01-30 9:44 ` [PATCH] ARM: dts: mvebu: add ethernet to the cm-a510 board Sebastian Hesselbarth
2015-01-30 9:44 ` Sebastian Hesselbarth
2015-01-30 9:44 ` Sebastian Hesselbarth
2015-01-30 10:31 ` Jean-Francois Moine
2015-01-30 10:31 ` Jean-Francois Moine
2015-01-30 11:00 ` Sebastian Hesselbarth
2015-01-30 11:00 ` Sebastian Hesselbarth
2015-01-30 11:00 ` Sebastian Hesselbarth
2015-01-30 11:41 ` Jean-Francois Moine
2015-01-30 11:41 ` Jean-Francois Moine
2015-01-30 11:41 ` Jean-Francois Moine
2015-01-30 12:03 ` Sebastian Hesselbarth
2015-01-30 12:03 ` Sebastian Hesselbarth
2015-01-30 12:03 ` Sebastian Hesselbarth
2015-01-30 12:39 ` Jean-Francois Moine
2015-01-30 12:39 ` Jean-Francois Moine
2015-01-30 12:50 ` Sebastian Hesselbarth
2015-01-30 12:50 ` Sebastian Hesselbarth
2015-01-30 12:50 ` Sebastian Hesselbarth
2015-02-01 14:12 ` Gabriel Dobato
2015-02-01 14:16 ` Gabriel Dobato
2015-02-05 22:13 ` Sebastian Hesselbarth
2015-02-05 22:13 ` Sebastian Hesselbarth
2015-02-06 7:58 ` Jean-Francois Moine [this message]
2015-02-06 7:58 ` Jean-Francois Moine
2015-02-06 7:58 ` Jean-Francois Moine
2015-02-06 10:05 ` Sebastian Hesselbarth
2015-02-06 10:05 ` Sebastian Hesselbarth
2015-02-06 10:05 ` Sebastian Hesselbarth
2015-02-06 10:50 ` Jean-Francois Moine
2015-02-06 10:50 ` Jean-Francois Moine
2015-02-06 10:52 ` Russell King - ARM Linux
2015-02-06 10:52 ` Russell King - ARM Linux
2015-02-06 10:48 ` Russell King - ARM Linux
2015-02-06 10:48 ` Russell King - ARM Linux
2015-02-06 9:19 ` Gabriel Dobato
2015-02-06 10:00 ` Sebastian Hesselbarth
2015-02-06 10:00 ` Sebastian Hesselbarth
2015-02-06 10:00 ` Sebastian Hesselbarth
2015-01-30 12:44 ` David Goodenough
2015-01-30 13:07 ` Sebastian Hesselbarth
2015-01-30 13:07 ` Sebastian Hesselbarth
2015-01-30 13:32 ` David Goodenough
2015-01-30 6:06 Jean-Francois Moine
-- strict thread matches above, loose matches on Subject: below --
2015-01-30 6:06 Jean-Francois Moine
2015-01-30 6:06 Jean-Francois Moine
2015-01-30 6:06 Jean-Francois Moine
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=20150206085855.7b8d494b@armhf \
--to=moinejf@free.fr \
--cc=linux-arm-kernel@lists.infradead.org \
/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.