public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: lamikr <lamikr@cc.jyu.fi>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Pending July patches
Date: Fri, 04 Aug 2006 17:40:28 +0300	[thread overview]
Message-ID: <44D35C5C.8060602@cc.jyu.fi> (raw)
In-Reply-To: <20060804110530.GC26416@atomide.com>

It would be nice if somebody could test the functionality of usbnet and
mmc/sd with omap1 devices (omap1510)
before tagging. I got the lcd working by using the fixes now already
applied to OMAP kernel but both the MMC/SD
and usbnet failed to work at least for me & h6300.
(2.6.16 kernel worked ok.)

I can also try to test again these but for me it will go over the weekend...

Mika

Tony Lindgren wrote:
> Hi all,
>
> I've pushed some patches. Does anybody else have patches that should go in
> before I tag 2.6.17-omap2?
>
>  Here's the current status:
>
> 1. [PATCH] fix PWL macro names
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-July/007503.html
>
> Pushed.
>
> 2. [PATCH] ARM: OMAP: Fix missing channel using
> omap_set_dma_priority()
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-July/007508.html
>
> Note: Needs check if channel 0 is really okay for OMAP24xx.
>
> This gets only called for omap1, channel does not matter. Pushed.
>
> 3. ARM: OMAP: omapfb: Fix 444 mode after recent LCD changes
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-July/007525.html
>
> Pushed.
>
> 4. [PATCH] ARM: OMAP: omapfb: Add Amstrad Delta LCD driver
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-July/007526.html
>
> Pushed.
>
> 5. 2420 boot BUG(): failure to map SRAM
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-July/007578.html
>
> Pushed.
>
> 6.[PATCH] ARM: OMAP: mux: add config for 16xx SPI pins
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-July/007596.html
>
> Pushed.
>
> 7. [PATCH] ARM: OMAP: Apollon MMC support using OMAP2 MMC interface
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-June/007373.html
>
> Pushed.
>
> 8. [PATCH] ARM: OMAP: LEDs dirver support
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-June/007478.html
>
> Pushed.
>
> 9. [PATCH] USB device support on OMAP2
> http://linux.omap.com/pipermail/linux-omap-open-source/2006-June/007471.html
>
> Not pushed yet, need to leave out MMC code out of the patch and test
> first.
>
> Regards,
>
> Tony
> _______________________________________________
> Linux-omap-open-source mailing list
> Linux-omap-open-source@linux.omap.com
> http://linux.omap.com/mailman/listinfo/linux-omap-open-source
>
>   

  parent reply	other threads:[~2006-08-04 14:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 16:44 Pending July patches Dirk Behme
2006-08-03 11:17 ` Tony Lindgren
2006-08-03 12:08   ` Komal Shah
2006-08-03 13:03     ` GPMC timings for smc91x on 24xx (WAS: Pending July patches) Tony Lindgren
2006-08-03 13:39       ` Need help to understand a #pragma statment Taru Varshney
2006-08-04 11:05     ` Pending July patches Tony Lindgren
2006-08-04 13:20       ` [PATCH] ARM: OMAP: Fix lcd_ams_delta to use new PWL defines Jonathan McDowell
2006-08-07 15:22         ` Tony Lindgren
2006-08-08  8:33           ` mcbsp Arnold
2006-08-08 21:33           ` 2.6.18-rc4 / generic irq etc Jonathan McDowell
2006-08-09  7:26             ` Tony Lindgren
2006-08-04 14:40       ` lamikr [this message]
2006-08-07 15:23         ` Pending July patches Tony Lindgren
2006-08-07 23:56           ` lamikr
2006-08-08  1:30             ` andrzej zaborowski
2006-08-10  4:41               ` andrzej zaborowski
2006-08-10  7:32                 ` Tony Lindgren
2006-08-10  8:07                   ` andrzej zaborowski
2006-08-10 10:45                     ` Tony Lindgren

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=44D35C5C.8060602@cc.jyu.fi \
    --to=lamikr@cc.jyu.fi \
    --cc=linux-omap-open-source@linux.omap.com \
    --cc=tony@atomide.com \
    /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