@ Dana Goyette,
The flag is already set in Maverick, please test with that kernel. If
this works to your convenience the bug will be back ported to Lucid.
Kernel:
https://edge.launchpad.net/ubuntu/maverick/armel/linux-image-2.6.34-5-omap/2.6.34-5.12
To install:
ubu...@beagleboard:~$ sudo dpkg
recognized by the kernel.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Mathieu Poirier (mathieu.poirier)
Status: Confirmed
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
SDHC card not recognized
https://bugs.launchpad.net/bugs/591941
You re
** Changed in: linux-ti-omap (Ubuntu Lucid)
Status: In Progress => Fix Committed
** Changed in: linux-ti-omap (Ubuntu)
Status: In Progress => Fix Released
--
wlan0 "Interface doesn't support scanning." -- CONFIG_CFG80211_WEXT is not set
https://bugs.launchpad.net/bugs/566238
You re
** Changed in: linux-ti-omap (Ubuntu)
Status: In Progress => Fix Committed
--
netinstall fails, it has no network driver for moschip
https://bugs.launchpad.net/bugs/584920
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
** Changed in: linux-ti-omap (Ubuntu)
Assignee: (unassigned) => Mathieu Poirier (mathieu.poirier)
** Changed in: linux-ti-omap (Ubuntu)
Status: New => Confirmed
--
wlan0 "Interface doesn't support scanning." -- CONFIG_CFG80211_WEXT is not set
https://bugs.laun
ignee: Mathieu Poirier (mathieu.poirier)
Status: New
** Changed in: linux-ti-omap4 (Ubuntu)
Assignee: (unassigned) => Mathieu Poirier (mathieu.poirier)
--
Screen goes blank and system seems unresponsive
https://bugs.launchpad.net/bugs/653002
You received this bug notification bec
Public bug reported:
The LEDs on the IGEPv2 board are not working.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Mathieu Poirier (mathieu.poirier)
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mathieu Poirier (mathieu.poirier)
--
Public bug reported:
There is 2 version of the board and there is currently no functionality
in the code to differentiate them.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Mathieu Poirier (mathieu.poirier)
Status: New
** Changed in: linux (Ubuntu)
Assignee
Public bug reported:
Some GPIO's used by WLAN-BT combo on IGEP v2 depends on hardware
revision - initialization need to be done properly.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Mathieu Poirier (mathieu.poirier)
Status: New
** Changed in: linux (U
Public bug reported:
EDID information needs to be exported to userspace in order to be
processed by 'decode-edid' and 'parse-edid'.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Mathieu Poirier (mathieu.poirier)
Status: New
** Chang
Public bug reported:
Since there is no VMMC2 regulator on the IGEPv2 board, declaration and
initialization code should be removed from the board file.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Mathieu Poirier (mathieu.poirier)
Status: New
** Changed in: linux
I've integrated all 6 patches submitted by Enric:
http://marc.info/?l=linux-arm-kernel&m=128596744515511&w=2
Can someone with an IGEPv2 board help me test the following:
http://people.canonical.com/~mpoirier/linux-image-2.6.35-22-omap_2.6.35-22.34_armel.deb
Many thanks, Mathieu.
--
VMMC2 regu
SRU Justification:
Impact: When booting the omapdss subsystem is looking for a regulator
named "vdds_sdi". When the regulator is not found the initialisation
sequence is aborted, resulting in omapfb not finding a display to work
with.
Fix: The problem was fixed by lumping a "vdds_sdi" with the a
Vincent Rabin is already mainlining those.
On Tue, 2011-01-18 at 22:40 +, John Rigby wrote:
> Mathieu, did the patches for this go upstream?
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/656375
I have tested with kernel http://launchpadlibrarian.net/58728585/linux-
image-2.6.35-23-omap_2.6.35-23.37_armel.deb and confirm the problem has
been resolved.
mpoir...@mpoirier-desktop:~$ uname -a
Linux mpoirier-desktop 2.6.35-23-omap #37-Ubuntu Sat Nov 6 02:01:12 UTC 2010
armv7l GNU/Linux
mpoir.
** Tags added: verification-done
** Tags removed: verification-needed
--
WLAN-BT GPIOs need proper initialization
https://bugs.launchpad.net/bugs/654590
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Public bug reported:
Dynamic Ftrace option is missing from Tracers menu on ARM
** Affects: linux-linaro (Ubuntu)
Importance: Undecided
Assignee: Mathieu Poirier (mathieu.poirier)
Status: New
** Changed in: linux-linaro (Ubuntu)
Assignee: (unassigned) => Mathieu Poir
SRU Justification:
Impact: This patch is part of a series of fix for the IGEPv2. The board
features 4 LED that must be declared and linked to GPIOs.
Fix: The LEDs are initialized and controlled via the LED class if
CONFIG_LEDS_GPIO is selected
or using the General Purpose Input/Output (GPIO) in
SRU Justification:
Impact: This patch is part of a series of fix for the IGEPv2. The board
features multiple GPIOs that must be initialized in order for signals to
be considered by the processor.
Fix: GPIOs for VBUS and over current are requested and their direction
set in the GPIO setup routine
SRU Justification:
Impact: This patch is part of a series for fix for the IGEPv2 board.
There are currently two version of the board but no functionality to
differentiate them from the code.
Fix: Introducing functionality in the board file to probe GPIOs and set
the "hwrev" flag.
Testcase: Witho
SRU Justification:
Impact: This patch is part of a series of fix for the IGEPv2 board.
Initialization of the GPIOs used by the WLAN-BT must be tailored to the
underlying HW.
Fix: The fix entails checking the "hwrev" flag and make the proper
configuration. This patch depends on [PATCH 3/6], appli
SRU Justification:
Impact: This patch is part of a series of fix for the IGEPv2 board. The
monitor's EDID information needs to be exported to userspace for
application such as 'decode-edid' and 'parse-edid' to decode.
Fix: To do this a 3rd "i2c_board_info" instance is declared and
initialized i
SRU Justification:
Impact: This patch is part of a series of fix for the IGEPv2 board. The
monitor's EDID information needs to be exported to userspace for
application such as 'decode-edid' and 'parse-edid' to decode.
Fix: To do this a 3rd "i2c_board_info" instance is declared and
initialized in
SRU Justification:
Impact: This patch is part of a serie of fix for the IGEPv2 board. The
VMMC2 regulator is configured but it's not used on the IGEP v2. Since
the code is contained to the IGEPv2 board file, it will not impact other
boards.
Fix: The fix consist in remove the declaration and in
2.626129] omapfb omapfb: failed to setup omapfb
[2.630950] omapfb: probe of omapfb failed with error -22
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Mathieu Poirier (mathieu.poirier)
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ma
A patch for the problem has been found here:
http://bazaar.launchpad.net/~beagleboard-
kernel/+junk/2.6-stable/revision/57
It doesn't apply properly and has SPI elements we don't need. I applied
a variation of the patch and the display is now working.
--
Display is not working on Gumstix Overo
SRU Justification
Impact: A power regulator named "vdds_sdi" is missing from the board
setup file, preventing the display sudbsystem from initializing
properly, something that impacts omapfb and yields a blank screen. DSS2
related platform data are also missing.
Fix: The fix consist in adding a
This is reproducible at will.
** Changed in: linux-ti-omap4 (Ubuntu)
Assignee: (unassigned) => Mathieu Poirier (mathieu.poirier)
--
BUG: scheduling while atomic: alsa-source/2058/0x0002
https://bugs.launchpad.net/bugs/644828
You received this bug notification because you are a mem
** Changed in: linux (Ubuntu Maverick)
Milestone: maverick-alpha-2 => maverick-alpha-3
--
No video on beagleboard with 2.6.35 kernels.
https://bugs.launchpad.net/bugs/597904
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
** Changed in: linux (Ubuntu Maverick)
Status: New => In Progress
--
No video on beagleboard with 2.6.35 kernels.
https://bugs.launchpad.net/bugs/597904
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The problem is caused by DSS devices not recognized by the kernel when
initializing the frame buffer subsystem.
The two DSS devices - "dvi" and "tv" - are both devifed and passed to
"platform_add_devices" in "board-omap3beagle.c"
For some reason they don't seem to make it to the "platform_device
The omapfb driver couldn't locate its display sink because of
an initialisation error in the DSS subsystem. This error was
caused by a missing 'vdds_sdi' entry in the board power regulator list.
** Changed in: linux (Ubuntu Maverick)
Status: In Progress => Fix Committed
--
No video on b
This seems to be related to yet another kernel config option:
- The code producing the error message is compiled in both upstream and
maverick branches.
- If the upstream branch is compiled with upstreams' .config file, the daisy
chain error messages don't show.
- If the upstream branch is compi
The problem seams to be related to a timing issue when reading
PM_WKST_WKUP, pulling for a daisy chain event. Introducing a simple
mdelay(5) between the write and read operation fixes the problem but it
is highly inefficient.
A real fix should follow shortly but in the mean time a kernel config
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux-ti-omap (Ubuntu)
Status: In Progress => Fix Committed
--
kernel BUG at
/build/buildd/linux-ti-omap-2.6.33/drivers/video/omap2/dss/core.c:323!
https://bugs.launchpad.net/bugs/588243
You receive
*** This bug is a duplicate of bug 588243 ***
https://bugs.launchpad.net/bugs/588243
** This bug has been marked a duplicate of bug 588243
kernel BUG at
/build/buildd/linux-ti-omap-2.6.33/drivers/video/omap2/dss/core.c:323!
--
DSS2 oops when shutting down while DPMS is active
https://bug
This issue seems to have been resolved in kernels newer than
2.6.33-500-omap-5. We haven't seen it in 2.6.33-502 nor in Maverick.
** Changed in: linux-ti-omap (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux-ti-omap (Ubuntu Lucid)
Status: Confirmed => Won't Fix
--
DS
*** This bug is a duplicate of bug 591941 ***
https://bugs.launchpad.net/bugs/591941
** This bug has been marked a duplicate of bug 591941
SDHC card not recognized
--
Timing issues with certain SD cards on beagleboard
https://bugs.launchpad.net/bugs/592688
You received this bug notificati
Bryan,
To get the OTG port in host mode one needs to ground the ID pin,
something that requires a soldering iron. Unless I find a way to do it
without the modification it will take me a couple of days to test your
image.
I will also get in touch with Oliver - after all he reported the problem
I have also seen this many times.
--
DSS2 oops when shutting down while DPMS is active
https://bugs.launchpad.net/bugs/563650
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
- posted request for help on "linux-o...@vger.kernel.org"
- got in contact with Jayabharath to get access to the original TI developers.
- have been working with TI developers on the problem.
- issue is related to DMA - transfers are coming back with a timeout error when
preemption model is set to
** Changed in: linux (Ubuntu)
Milestone: None => maverick-alpha-3
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mathieu Poirier (mathieu.poirier)
--
i2c support for edid on armel
https://bugs.launchpad.net/bugs/608279
You received this bug notification because you
parse-edid demands binary date, something i2cdump doesn't provide.
I added an additional 'i2c_board_info' structure and tied it to the i2c
'eeprom' driver, which creates the following
/sys/bus/i2c/devices/3-0050/eeprom entry. From there using 'decode-
edid' specifying to scan bus 3 is trivial. N
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
i2c support for edid on armel
https://bugs.launchpad.net/bugs/608279
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Public bug reported:
GPIO's for external VBUS power switch and overcurrent detect on IGEP v2
board are missing.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Mathieu Poirier (mathieu.poirier)
Status: Confirmed
** Changed in: linux (Ubuntu)
Status
** Changed in: ubuntu-cdimage
Assignee: (unassigned) => Mathieu Poirier (mathieu.poirier)
--
Preinstalled Maverick netbook image has no display on omap3 EVM (no LCD)
https://bugs.launchpad.net/bugs/630885
You received this bug notification because you are a member of Ubuntu
Bugs, which
I fixed bug 597904 and I suspect the same problem is happening here - it
probably stems from a missing regulator declaration in the board
specific file.
Vincent, what board are you booting this on ?
--
Preinstalled Maverick netbook image has no display on omap3 EVM (no LCD)
https://bugs.launchpa
le board.
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-cdimage
Status: Invalid => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mathieu Poirier (mathieu.poirier)
--
Preinstalled Maverick netbook image has no display
Bien évidamment que je pouvais pas l'avoir du premier coup...
Ok, j'y travaille.
Mathieu.
On Mon, 2010-09-13 at 21:45 +, Vincent Stehlé wrote:
> Mathieu, thanks for your concern!
>
> FYI: My board is an OMAP3 EVM rev. D (See
> http://www.mistralsolutions.com/products/omap_3evm.php).
>
> I
"sdi_init" (dss/sdi.c:159), called by "omap_dss_probe" (dss/core.c:496)
is specifically looking for a regulator named "vdds_sdi", something that
isn't part of the patch I applied (see above) but part of the patch
provided in #6.
Attached is the patch I used to generate
"http://people.canonical.com
Robert,
I've seen this issue with all type and sizes. Aside from the above
stated trick of configuring the kernel with PREEMPT_NONE rather than
PREEMPT_VOLUNTARY, disabling the "CPU Power Management" options
(CONFIG_CPU_FREQ and CONFIG_CPU_IDLE) will also fix the problem.
Experimenting with CONF
On Wed, 2010-08-04 at 18:10 +, Robert Nelson wrote:
> Hi Lee,
>
> No dice..
>
> I modified my config with:
>
> -# CONFIG_CPU_IDLE is not set
> +CONFIG_CPU_IDLE=y
> +CONFIG_CPU_IDLE_GOV_LADDER=y
> +CONFIG_CPU_IDLE_GOV_MENU=y
>
> It finds the mmc card just fine, mounts card, login, etc...
>
This is the upstream version of the ubuntu config file that will cause
the mmc card to fail during bootup time. It was generated with upstream
2.6.35-rc6. You should simply be able to checkout, make oldconfig, make
uImage and get a binary that will exhibit the behavior.
My u-boot "bootargs" look
This is a uImage that was generated by compiling 2.6.35-rc6 with the
above posted config file. To know if your card is subject to the
failure, simply boot with this kernel and watch out for the " mmc0:
error -110 whilst initialising SD card" error message.
Obviously, booting with this kernel will
The uImage I posted is for a beagleboard C4 - I haven't tried with a XM.
On Thu, 2010-08-05 at 21:36 +, Robert Nelson wrote:
> Loosing my mind, so let's reset some things.. ;)
>
> Mathieu, did you happen to boot the uImage posted in Message #9 on a XM?
>
> I get this on my XM:
>
> mmc1 is a
Glad you were able to reproduce - the failure is indeed present on the
Cx models but wouldn't know about the Bx.
On Thu, 2010-08-05 at 23:17 +, Robert Nelson wrote:
> Okay, finally replicated the -110 error on 2.6.35 with my XM
>
> Minimal 2.6.35 tree, using Mathieu's config, on my XM:
>
>
Stanley Miao's patch has been submitted and should be applied shortly:
http://bugs.launchpad.net/bugs/588243
--
kernel BUG at
/build/buildd/linux-ti-omap-2.6.33/drivers/video/omap2/dss/core.c:323!
https://bugs.launchpad.net/bugs/588243
You received this bug notification because you are a membe
The problem came from the gpmc not being initialized before accessing
the nand flash. Gpmc and the nand flash driver were decoupled after
Lucid and the change was not reflected in "omap3beagle_flash_init".
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
[regression]
I was able to read the EDID without any kernel modification:
mpoir...@beagle:~$ uname -a
Linux beagle 2.6.35-15-omap #22 Thu Aug 12 16:23:35 EDT 2010 armv7l GNU/Linux
mpoir...@beagle:~$
mpoir...@beagle:~$ sudo apt-get install i2c-tools
mpoir...@beagle:~$
mpoir...@beagle:~$ sudo modprove i2c-dev
mp
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
[regression] no more /dev/mtdblock devices on omap3 in maverick
https://bugs.launchpad.net/bugs/608266
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
The driver is compiled in but the flash start address is not properly
set. Initialization of mtd device changed between Lucid and Maverick.
Base address seems to have been left out.
--
[regression] no more /dev/mtdblock devices on omap3 in maverick
https://bugs.launchpad.net/bugs/608266
You rece
61 matches
Mail list logo
