2012/10/5 Javier Martinez Canillas :
> On Fri, Oct 5, 2012 at 10:10 AM, Thomas Petazzoni
> wrote:
>>
>> On Fri, 5 Oct 2012 09:32:07 +0200, Javier Martinez Canillas wrote:
>>
>>> As Enric said, u-boot has SPL and NAND support for IGEP since
>>> v2012.10-rc1. I just tried kernel a 3.6 with u-boot v2
2012/4/23 Laurent Pinchart :
> The supply is connected to the DSS DO-D5 pins and is thus needed for
> both serial and parallel display interfaces on the igep0030 as well as
> the igep0020.
>
> If the igep0030 module isn't connected to a display, no DSI or DPI
> display will be specified in board co
2012/4/4 Javier Martinez Canillas :
> IGEP-based boards can have two different flash memories, a OneNAND or
> a NAND device. The boot configuration pins (sys_boot) are used to
> specify which memory is available.
>
> Also, this patch removes unnecesary code for registering the OneNAND.
>
> Signed-o
2012/4/4 Javier Martinez Canillas :
> board_onenand_init() and board_nand_init() initialization functions are
> used to initialize OneNAND and NAND memories respectively. But only
> board_nand_init() was visible to be used from board code. This patch makes
> possible to initialize a OneNAND flash m
2011/9/12 Tomi Valkeinen :
> On Mon, 2011-09-12 at 11:58 +0200, Enric Balletbò i Serra wrote:
>> 2011/9/12 Tomi Valkeinen :
>> > Add i2c bus number for DVI output. The driver uses this to detect if a
>> > panel is connected and to read EDID.
>> >
2011/9/12 Tomi Valkeinen :
> Add i2c bus number for DVI output. The driver uses this to detect if a
> panel is connected and to read EDID.
>
> Signed-off-by: Tomi Valkeinen
> ---
> arch/arm/mach-omap2/board-omap3beagle.c | 1 +
> arch/arm/mach-omap2/board-omap4panda.c | 1 +
> arch/arm/mac
Hi all,
Playing with USB ethernet gadget on IGEP boards with mainline kernel
(Linux 3.0.0-rc7) I observed one strange behavior. The ethernet gadget
works with one board with OMAP3530 but it doesn't with another one
with DM3730. The log looks like this:
root@igep00x0:~# modprobe g_ether
[ 51.42
Hi,
2011/5/17 Tony Lindgren :
> * Enric Balletbò i Serra [110516 10:11]:
>> Hi Mike,
>>
>> The only comment I wanted to do is maybe I prefer rename the
>> board-igep0020 to board-igep00x0 to be more generic. Apart from this
>> these patch series looks good for
2011/5/12 Mike Rapoport :
> since it is merged into board-igep0020.c
>
> Signed-off-by: Mike Rapoport
> ---
> arch/arm/mach-omap2/Kconfig | 1 +
> arch/arm/mach-omap2/Makefile | 2 -
> arch/arm/mach-omap2/board-igep0030.c | 438
> --
> 3 fi
2011/5/15 Arnd Bergmann :
> On Sunday 15 May 2011, m...@compulab.co.il wrote:
>> We can keep all the data structures that differ between IGEP2 and IGEP3.
>> However, this significantly reduces the benifit of the series.
>> There's already code in the IGEP2 that differentiates between HW
>> revision
2011/5/12 Mike Rapoport :
> Add IGEP3 machine support to board-igep0020
>
> Signed-off-by: Mike Rapoport
> ---
> arch/arm/mach-omap2/board-igep0020.c | 103
> ++
> 1 files changed, 80 insertions(+), 23 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-igep0
Hi Mike,
The only comment I wanted to do is maybe I prefer rename the
board-igep0020 to board-igep00x0 to be more generic. Apart from this
these patch series looks good for me and has my ack. Thanks.
2011/5/12 Mike Rapoport :
> IGEP2 and IGEP3 boards are very similar and can be merged into one fi
Hi Mike,
2011/5/12 Mike Rapoport :
> Hi Tony,
>
> I'm resending this with the correct arm-linux mailing list cc'ed..
> Just discard the first set, sorry for the noise...
>
> This is yet another attempt to reduce code duplication in the board files :)
> Only build tested, since I don't have the har
2011/5/4 Igor Grinberg :
> On 05/03/11 20:25, Enric Balletbò i Serra wrote:
>
>> Hi guys,
>> I'm thinking probably in a crazy idea, I hope someone can help me or
>> kill definitely this idea from my mind.
>
> This is not that crazy as you think it is...
>
&
2011/5/4 Vladimir Pantelic :
> Enric Balletbò i Serra wrote:
>>
>> Hi guys,
>> I'm thinking probably in a crazy idea, I hope someone can help me or
>> kill definitely this idea from my mind.
>>
>> I'll explain a little more, the real problem is I
Hi guys,
I'm thinking probably in a crazy idea, I hope someone can help me or
kill definitely this idea from my mind.
I'll explain a little more, the real problem is I don't know how to
add support for an expansion board for IGEP v2 board. I see most of
boards adds the support inside the board-xxx
Hi,
2011/4/7 Alan Stern :
> On Thu, 7 Apr 2011, Enric Balletbò i Serra wrote:
>
>> Hi all,
>>
>> I'm experimenting some issues with USB on IGEP v2 board, in certain
>> cases I've an USB disconnect when I plug a device. For me it fails
>> with kernel
the board with the USB HUB connected to the USB Host
port and the device connected to the USB hub.
2. if after kernel is up, connect the USB HUB + device to the USB Host port
Anyone is experimenting something like this with other OMAP3-based boards ?
Regards,
Enric Balletbò i Serra
--
To u
2010/12/13 Tony Lindgren :
> * Enric Balletbò i Serra [101213 08:47]:
>>
>> Tony, please can this patch be included before 2.6.37 ? Without this
>> patch the wifi module on IGEP v2 board not works.
>
> Sorry it's too much for the -rc series. For the -rc series
Hi all,
2010/12/4 Marc Zyngier :
> Commit 72f381ba056 (omap3: Remove VMMC2 regulator on IGEP v2)
> removed an unused regulator entry, but left the second MMC channel
> (used by the Libertas WLAN module) without link to power regulator.
> This causes the SDIO module to fail being detected.
>
> This
2010/12/12 Laurent Pinchart :
> Make sure the LED is turned off at boot time, and configure the GPIO LED
> device as active low.
>
> Signed-off-by: Laurent Pinchart
> ---
> arch/arm/mach-omap2/board-igep0020.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/arch/ar
2010/12/12 Laurent Pinchart :
> gpio_direction_output() has a value argument, there's no need to call
> gpio_set_value() explicitly right after.
>
> Signed-off-by: Laurent Pinchart
> ---
> arch/arm/mach-omap2/board-igep0020.c | 20
> 1 files changed, 8 insertions(+), 12 del
Hi,
2010/11/14 Marc Zyngier :
> On Sun, 14 Nov 2010 19:11:46 +0100
> Enric Balletbò i Serra wrote:
>
>> Why we need to define an unexistent regulator in board file ? This
>> should not be done enabling the CONFIG_DUMMY_REGULATOR in your kernel
>> configuration ?
2010/11/14 Felipe Balbi :
> Hi,
>
> On Sun, 14 Nov 2010 11:34:12 +, Marc Zyngier
> wrote:
>> @@ -272,8 +273,8 @@ static struct regulator_init_data igep2_vmmc1 = {
>> | REGULATOR_CHANGE_MODE
>> | REGULATOR_CHANGE_STATUS
Hi,
2010/11/5 Ming Lei :
> 2010/11/5 Grazvydas Ignotas :
>> hi,
>>
>> On Fri, Nov 5, 2010 at 10:39 AM, Enric Balletbò i Serra
>> wrote:
>>> Hello all,
>>>
>>> With current mainline and stable 2.6.35.y branch I've some strange
>&
Hello all,
With current mainline and stable 2.6.35.y branch I've some strange
features with USB ethernet gadget ...
r...@igep0020:~# uname -a
Linux igep0020 2.6.37-rc1+ #1 Fri Nov 5 09:22:53 CET 2010 armv7l
unknown unknown GNU/Linux
r...@igep0020:~# ifconfig
usb0 Link encap:Ethernet
Hi all,
2010/10/10 Mike Rapoport :
> Hi Madhu,
>
> Madhusudhan wrote:
>>
>>> -Original Message-
>>> From: Steve Sakoman [mailto:sako...@gmail.com]
>>> Sent: Thursday, October 07, 2010 8:57 AM
>>> To: Mike Rapoport
>>> Cc: Madhusudhan Chikkature; David Vrabel; Chris Ball; linux-
>>> m...@vg
Hello all,
Can I add a new omap_dss_device after dss_device registration ?
Something like add_new_omap_dss_device(lcd_device) or similar ?
On IGEP v2 we register only igep2_dvi_device as dss_device, We want to
add a new dss_device (igep2_lcd_device) after dss registration. Is it
possible ?
For
Hello all,
I would ask some technical questions, maybe someone can help me. I
would add support for a new expansion board for IGEP v2 board,
The expansion board comes with a EEPROM, the EEPROM is used to
identify the expansion board, my idea is create a new file for
expansion board ( board-igep00
Hello,
2010/10/5 David Cohen :
> On Sat, Oct 02, 2010 at 12:12:32PM +0200, ext Enric Balletbò i Serra wrote:
>> 2010/10/2 David Cohen :
>> > Hi,
>> >
>> > On Fri, Oct 01, 2010 at 11:09:04PM +0200, ext Enric Balletbo i Serra wrote:
>> >> GPI
2010/10/2 David Cohen :
> Hi,
>
> On Fri, Oct 01, 2010 at 11:09:04PM +0200, ext Enric Balletbo i Serra wrote:
>> GPIO for various devices are missing from the board initialization.
>> This patch adds support for the VBUS and over current gpios. Without this
>> patch, input/outputs from these two s
2010/10/2 Tony Lindgren :
> * Enric Balletbo i Serra [101001 15:18]:
>> The OMAP3 IGEP module is a low-power, high performance production-ready
>> system-on-module (SOM) based on TI's OMAP3 family.
>
> Looks OK to me, but also looks like you're missing the uncompress.h
> DEBUG_LL/EARLY_PRINTK entr
2010/7/14 Gadiyar, Anand :
> Enric Balletbò i Serra
>> Hello,
>>
>> When I disconnect an USB pendrive using twl4030 otg as host (step 2)
>> the usb_disconnect function is not called. OTOH if I reconnect the
>> device (step 3), then the usb_disconnect function is c
Hello,
When I disconnect an USB pendrive using twl4030 otg as host (step 2)
the usb_disconnect function is not called. OTOH if I reconnect the
device (step 3), then the usb_disconnect function is called.
Does anyone have any ideas why usb_disconnect is not called when the
device is removed?
Step
Hello,
2010/7/8 Artem Bityutskiy :
> On Thu, 2010-07-08 at 12:11 +0200, Enric Balletbò i Serra wrote:
>> Hello,
>>
>> 2010/7/8 Artem Bityutskiy :
>> > On Thu, 2010-07-08 at 11:55 +0200, Enric Balletbò i Serra wrote:
>> >> Hello,
>> >>
>&
Hello,
2010/7/8 Artem Bityutskiy :
> On Thu, 2010-07-08 at 11:55 +0200, Enric Balletbò i Serra wrote:
>> Hello,
>>
>> I made new tests regarding this issue. Looks like the problem is
>> reading from the OneNAND device.
>
> Did you try older kernel and then bis
at
: checking...
compare failed. seed 1804289383
Byte 0x1 is 5a should be da
Byte 0x3 is 82 should be 92
(...)
I suspect currently OneNAND with 2 planes is broken. Someone with this
type of device can try these tests ?
Thanks in advance,
Enric
2010/5/12 Enric Balletbò i Serra
Hello,
I need some help to understand what is wrong, maybe someone can help me.
I'm running an OMAP3-based board with a OneNAND from Numonyx, the
problem is some mtd tests fails. An example is the mtd_pagetest, the
erase test fails.
[ 937.885925] mtd_pagetest: erasetest
[ 937.889434] mtd_paget
I answer to myself.
DDP (dual die plane) not implies 'ONENAND_HAS_2PLANE'. A device with
a single die can also have '2 planes'. I'm right ?
Sorry for these newbie questions, I'm just introducing to OneNAND devices.
Cheers,
Enric
2010/5/12 Enric Balletbò i Serra
'Chip has 2 plane' ?
Sorry if this is a trivial question but I'm not sure about DDP and '2
plane' concepts. Are the same ?
Cheers,
Enric
2010/5/6 Enric Balletbò i Serra :
> Hi,
>
> 2010/5/6 Kyungmin Park :
>> Hi,
>>
>> What's your c
nd two-plane NAND Flash memory array,
These two component enables simultaneous program of 4KiB (
CONFIG_MTD_ONENAND_2X_PROGRAM)
Cheers,
Enric
>
> Thank you,
> Kyungmin Park
>
> On Thu, May 6, 2010 at 8:22 PM, Enric Balletbò i Serra
> wrote:
>> Hi,
>>
>> 2010
25.677978] onenand_command[382] page 1407, 2752512, 63
: checking...
Finished pass 1 successfully
--- end log nandtest pass ---
>
> In my test environment, it displays the correct page number.
> (addr - onenand_addr(this, block) >> this->page_shift is same as
> '(addr
Hello all,
After commit 5988af2319781bc8e0ce418affec4e09cfa77907 (mtd:
Flex-OneNAND support) the onenand support for my device is broken.
Before this commit when I run the nandtest program all is ok
---
# nandtest /dev/mtd3
ECC corrections: 0
ECC failures : 0
Bad blocks : 0
BBT blocks :
Hi,
2010/3/15 Felipe Balbi :
> Hi,
>
> please don't top-post. Read more at [1].
Sorry
> is there a IGEP v1 board available ? Are there any developers around
> using it ? If true, you should try to be backwards compatible.
Yes, IGEP v1 is available but it's a different platform with different pr
Hello,
Felipe, sorry but I don't understand your questions,m maybe I'm
missing something.
All IGEP v2 boards uses USB1HS EHCI port. My mistake was suppose that
port_mode[1] --> EHCI USB1HS but this is not correct, the EHCI USB1HS
is port_mode[0]. This patch only fixes this.
Best regards,
Enric
For me also works, thanks
Best regards,
Enric
2010/3/4 Tomi Valkeinen :
> On Thu, 2010-03-04 at 16:25 +0100, ext Enric Balletbò i Serra wrote:
>> Hello,
>>
>> Testing the Linux Omap master branch on IGEP v2 board I get this feature
>>
>> [ 17.565155] omapfb o
Hello,
Testing the Linux Omap master branch on IGEP v2 board I get this feature
[ 17.565155] omapfb omapfb: cannot parse default modes
My kernel command line is something like '..
omapfb.mode=dvi:1280x720mr...@60' which works without problems with
latest 2.6.33-rc8. Any idea about this ? Ther
could be
> due to negotiation of voltage.
>
> I would look at these things first.
>
> Regards,
> Madhu
>
> ________
> From: Enric Balletbò i Serra [mailto:eballe...@gmail.com]
> Sent: Tuesday, January 05, 2010 10:44 AM
> To: linux-omap@vg
Hi all,
I'm having problems trying to run the SDIO WLAN module on my IGEP v2
board using the latest omap kernel (2.6.33-rc2). The SDIO WLAN module
is connected to the MMC2 using 4 wires. With an older kernel ( 2.6.28
) works fine but the same configuration with 2.6.33-rc2 do not detect
the SDIO ca
> This part isn't relevant to ASoC. Shouldn't it go separately through
> linux-omap?
>
> It could possibly get folded into the patch adding this board support in the
> first place.
>
> - Anand
Oops, sorry is a mistake I will resend the patch without this.
Thanks,
Enric
2009/11/18 Gadiyar, Anan
Hi all,
I would like to add support for SoC audio on the IGEP v2 board but I
have some doubts about how to do. As I have seen in the source code,
the SoC driver for IGEP should be the same as omap3evm, overo and
cm-t35.
So, is better to use the solution adopted by the board CM-T35 or add a
specif
Signed-off-by: Enric Balletbo i Serra
---
arch/arm/configs/igep0020_defconfig | 1432 +++
1 files changed, 1432 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/configs/igep0020_defconfig
diff --git a/arch/arm/configs/igep0020_defconfig
b/arch/arm/config
This patch adds minimal IGEP v2 support.
The IGEP v2 board is a low-cost, fan-less and industrial temperature
range single board computer that unleashes laptop-like performance and
expandability without the bulk, expense, or noise of typical desktop
machines. Its architecture shares much in common
Ok, I will resubmit in few minuts
Thanks,
Enric
2009/10/13 Tony Lindgren :
> * Enric Balletbò i Serra [091009 09:18]:
>> This patch adds minimal IGEP v2 support.
>
> Can you please move the defconfig into a separate patch
> when you resubmit? It makes it easier for pe
This patch adds minimal IGEP v2 support.
The IGEP v2 board is a low-cost, fan-less and industrial temperature
range single board computer that unleashes laptop-like performance and
expandability without the bulk, expense, or noise of typical desktop
machines. Its architecture shares much in common
www.igep-platform.com
Regards,
Enric
2009/10/10 Nishanth Menon :
> Hi,
> Thanks for the patch.. a few minor comments follow from a read through..
>
> Enric Balletbò i Serra had written, on 10/09/2009 10:59 AM, the following:
>>
>> This patch adds minimal IGEP v2 support.
&
This patch adds minimal IGEP v2 support.
Signed-off-by: Enric Balletbo i Serra
---
arch/arm/configs/igep0020_defconfig | 1443 ++
arch/arm/mach-omap2/Kconfig |4 +
arch/arm/mach-omap2/Makefile |2 +
arch/arm/mach-omap2/board-igep0020.c
Hi all,
I'm a newbie and I have some questions. What is the procedure to
publish our patches to add support for a new OMAP3 based board ? Can I
send the patches to this list ?
Thanks in advance,
Enric
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" i
58 matches
Mail list logo
