From: linux@johnea.net
To: linux-omap@vger.kernel.org
Subject: Which git to clone for testing prior to submitting bugs?
Date: Thu, 27 Sep 2012 10:19:30 -0700 [thread overview]
Message-ID: <50648AA2.2010004@johnea.net> (raw)
Hello,
We're developing a system based on DM3730, and using Beagleboard-xM as a prototype platform.
The 3.2 series kernels provided a working video output on Beagleboard-xM integrated HDMI connector.
We use the kernel parameters: omapfb.mode=dvi:800x480MR-24@60 omapfb.vram=0:6M,1:2M,2:2M omapdss.def_disp=dvi
We upgraded to kernel 3.4.3 in order to take advantage of the kernel parameter: buddy=spidev
This provided spidev access without requiring that we build a custom kernel.
However in the 3.4 series, dvi output no longer works.
In a subsequent distro upgrade to 3.4.4 neither dvi, nor buddy=spidev function anymore.
I'd like to test the latest appropriate kernel prior to considering these issues as current bugs.
Can someone please advise which git tree to clone, for testing and possible bisect, prior to reporting bugs to this list?
Thank You
John Andrews
linux@johnea.net
next reply other threads:[~2012-09-27 17:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 17:19 linux [this message]
2012-09-27 18:25 ` Which git to clone for testing prior to submitting bugs? Robert Nelson
2012-09-27 18:56 ` linux
2012-09-27 18:55 ` Felipe Balbi
2012-09-27 19:17 ` Tony Lindgren
2012-09-27 19:27 ` Robert Nelson
2012-09-27 19:39 ` Robert Nelson
2012-09-27 20:16 ` linux
2012-09-27 20:41 ` Robert Nelson
2012-09-28 18:49 ` linux
2012-09-28 19:18 ` Robert Nelson
2012-09-28 19:46 ` linux
2012-10-01 14:57 ` johnea
2012-10-01 16:50 ` Robert Nelson
2012-10-01 16:57 ` linux
2012-10-01 21:16 ` linux
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=50648AA2.2010004@johnea.net \
--to=linux@johnea.net \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox