Re: Which git to clone for testing prior to submitting bugs?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Sep 27, 2012 at 12:19 PM,  <linux@xxxxxxxxxx> wrote:
>
> 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.

"buddy=xyz" is not upstream, so which 'tree'/'patchset' are you
currently using as a basis for your device?  The authors of that
patchset might be able to help out..

> 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?

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux