From: Anand Gadiyar <[EMAIL PROTECTED]>
Add pin-mux settings for OHCI in PHY mode.
Also change settings for EHCI in TLL mode.
Signed-off-by: Anand Gadiyar <[EMAIL PROTECTED]>
---
arch/arm/mach-omap2/mux.c | 67 +++---
arch/arm/plat-omap/include/mach/mux.
From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
Make hdq_reg_out as void and remove suspend, resume from the driver structure.
Signed-off-by: Madhusudhan Chikkature <[EMAIL PROTECTED]>
---
drivers/w1/masters/omap_hdq.c | 12 +---
1 files changed, 5 insertions(+), 7 deletions(-)
Index
From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
This patch fixes the indentation, commenting style of a single line comment.
Signed-off-by: Madhusudhan Chikkature <[EMAIL PROTECTED]>
---
drivers/w1/masters/omap_hdq.c | 81 +++---
1 files changed, 29 inserti
From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
This patch moves the shared variable into the local structure and
protects its updation.
Signed-off-by: Madhusudhan Chikkature <[EMAIL PROTECTED]>
---
drivers/w1/masters/omap_hdq.c | 52 ++
1 files changed
From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
This patch fix the exit paths in the probe function.
Signed-off-by: Madhusudhan Chikkature <[EMAIL PROTECTED]>
---
drivers/w1/masters/omap_hdq.c | 85 ++
1 files changed, 45 insertions(+), 40 deletions(-)
From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
This patch replaces the usage of semaphore by mutex.
Signed-off-by: Madhusudhan Chikkature <[EMAIL PROTECTED]>
---
drivers/w1/masters/omap_hdq.c | 42 ++
1 files changed, 22 insertions(+), 20 deletions(-)
From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
This patch provides the ioremap related changes to the driver.
Signed-off-by: Madhusudhan Chikkature <[EMAIL PROTECTED]>
---
drivers/w1/masters/omap_hdq.c | 21 ++---
1 files changed, 14 insertions(+), 7 deletions(-)
Index: linu
From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
Convert declaration to static.
Signed-off-by: Madhusudhan Chikkature <[EMAIL PROTECTED]>
---
drivers/w1/masters/omap_hdq.c | 10 +-
1 files changed, 5 insertions(+), 5 deletions(-)
Index: linux-omap-2.6/drivers/w1/masters/omap_hdq.c
===
From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
Remove the unneeded "unlikely" calls.
Signed-off-by: Madhusudhan Chikkature <[EMAIL PROTECTED]>
---
drivers/w1/masters/omap_hdq.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
Index: linux-omap-2.6/drivers/w1/masters/omap_hdq.
From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
Replace pr_debug with dev_dbg with device information added for
debug prints.
Signed-off-by: Madhusudhan Chikkature <[EMAIL PROTECTED]>
---
drivers/w1/masters/omap_hdq.c | 54 +++---
1 files changed, 30 insert
From: Madhusudhan Chikkature <[EMAIL PROTECTED]>
This patch provides the necessary modifications to the driver to
remove the global ptr hdq_data.
Signed-off-by: Madhusudhan Chikkature <[EMAIL PROTECTED]>
---
Sending this series on behalf of Madhu
drivers/w1/masters/omap_hdq.c | 137 +++
> -Original Message-
> From: [EMAIL PROTECTED] On Behalf Of Chikkature Rajashekar, Madhusudhan
> - Original Message - From: "Felipe Balbi" <[EMAIL PROTECTED]>
>
> > On Wed, Sep 24, 2008 at 05:01:27PM +0530, ext Madhusudhan Chikkature wrote:
> >> From: Madhusudhan Chikkature<[EMAIL
> On Mon, Sep 22, 2008 at 08:51:29PM +0530, ext Gadiyar, Anand wrote:
> > > From: [EMAIL PROTECTED] On Behalf Of Felipe Balbi
> > >
> > > On Mon, Sep 15, 2008 at 12:11:46AM +0530, Vikram Pandita wrote:
> > > > Better still is to move the PHY issues to
> From: [EMAIL PROTECTED] On Behalf Of Felipe Balbi
>
> On Mon, Sep 15, 2008 at 12:11:46AM +0530, Vikram Pandita wrote:
> > Better still is to move the PHY issues to platform/board specific function.
> > Will try to submit a patch on that.
>
> Any updates on this ?? Could you test the patches I s
>> "Gadiyar, Anand" <[EMAIL PROTECTED]> writes:
>>>
>>> On Saturday 23 August 2008, Tony Lindgren wrote:
>>> >
>>> > > I'll get the ehci-omap code in better shape and submit separately to the
>>> > > linux-u
>
> On Saturday 23 August 2008, Tony Lindgren wrote:
> >
> > > I'll get the ehci-omap code in better shape and submit separately to the
> > > linux-usb list.
>
> Given that we've not yet seen patches splitting out the board-specific
> bits into arch/arm/mach-omap2, I can't imagine those fixes bei
Hi Felipe, Paul,
> -Original Message-
> From: [EMAIL PROTECTED] On Behalf Of Felipe Balbi
> Hi,
>
>
> On Mon, Sep 15, 2008 at 12:11:46AM +0530, Pandita, Vikram wrote:
> > The issues mentioned are _not_ of omap34xx silicon, but of
> > the PHY (ISP1504 in SDP-USB expansion board).
>
> Go
> From: Felipe Balbi [EMAIL PROTECTED]
> On Sat, Sep 13, 2008 at 01:31:12AM +0530, Gadiyar, Anand wrote:
> > Was planning on cleaning up this driver and sending to linux-omap as Tony
> > suggested, but I'm afraid I won't be able to look at it for a while.
> >
> From: David Brownell [EMAIL PROTECTED]
> On Friday 12 September 2008, Gadiyar, Anand wrote:
> > 1. TLL vs PHY mode needs to be set somewhere. Me thinks this information
> > ought
> > to come from board-specific data and the driver would need to set things up
> >
> On Behalf Of Felipe Balbi [EMAIL PROTECTED]
> On Fri, Sep 12, 2008 at 12:21:59PM -0700, Tony Lindgren wrote:
> > * David Brownell <[EMAIL PROTECTED]> [080912 12:18]:
> > > On Friday 12 September 2008, Felipe Balbi wrote:
> > > > /* Enusre bit is set */
> > >
> > > My Cortex Mark-I (cerebr
From: Anand Gadiyar <[EMAIL PROTECTED]>
The Index register needs to be zero to access CONFIGDATA.
musb_ep_select()will not set the MUSB_INDEX register unless INDEXED
mode addressing is used. This change will set the register correctly
in INDEXED as well as FLAT mode.
Signed-off-by: Anand Gadiyar
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of stanley.miao
>
> In RGB565 mode, red and blue color are filtered, so the picture on LCD
> looks green and dark.
>
> Fix omapfb's problem on OMAP3430sdp.
>
> Signed-off-by: Stanley Miao <[EMAIL PROT
> > Hold off on this one. I'll send a better version to linux-usb
> > with a CC to linux-omap.
>
> Great. It's dropped. Care to update the MAINTAINERS file as well :-)
>
Will do. I need to fold in one more patch sent by Vikram and clean up
stuff a little. Then I'll send it across.
- Anand
--
To
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Felipe Balbi
> Sent: Saturday, August 30, 2008 10:46 PM
> To: linux-omap@vger.kernel.org
> Cc: Felipe Balbi
> Subject: [PATCH 29/33] add omap ehci bus glue
>
> From: Felipe Balbi <[EMAIL PROTECTED]>
>
>
> > How about reading the pin-mux registers directly?
>
> That's the backup plan. I was hoping there might be the equivalent of
> the pxaregs utility for the pxa architecture - it produces a nicely
> formatted text report of the current state of all pins and even allows
> you to modify them.
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Steve Sakoman
>
> Is anyone aware of a utility to report the state of pin mux settings?
>
> I'd like to verify that u-boot is setting things up properly.
How about reading the pin-mux registers direc
> > >
> > > Hmm... you got it working with v2.6.26... I'll bisect between that and
> > > HEAD so.
> > >
> >
> > I'm guessing you didn't see my previous mail [1].
> >
> > Last known good commit is 509f205d6. That'll save you an iteration at least.
> > You can go from there, but there's nothing
> -Original Message-
> From: Felipe Balbi [mailto:[EMAIL PROTECTED]
> On Fri, Aug 29, 2008 at 02:06:45PM +0530, ext Gadiyar, Anand wrote:
> > > On Fri, Aug 29, 2008 at 10:11:00AM +0530, ext Gupta, Ajay Kumar wrote:
> > > >
> > > >
> On Fri, Aug 29, 2008 at 10:11:00AM +0530, ext Gupta, Ajay Kumar wrote:
> >
> > I tested MUSB controller on OMAP35xx EVM
> (omap3_evm_defconfig) for g_ether gadget and it works fine
> with Windows XP. I am using v2.6.26-omap2 tag.
>
> ehehe, cool. So looks like the problem is either on tusb601
ECTED] On Behalf Of Felipe Balbi
> Sent: Thursday, August 28, 2008 4:51 PM
> To: Felipe Balbi
> Cc: Gadiyar, Anand; ext David Brownell; ext Ashwin Bihari;
> linux-omap@vger.kernel.org
> Subject: Re: Enabling MUSB support
>
> On Thu, Aug 28, 2008 at 01:28:42PM +0300, Felipe Ba
> On Wed, Aug 27, 2008 at 11:54:28PM -0700, David Brownell wrote:
> > On Wednesday 27 August 2008, Felipe Balbi wrote:
> > > I tried musb on omap2420 (with tusb), omap3430 and omap3530
> > > (beagle board) and all of them are working.
> >
> > I tried it on Beagle and found that OTG mode wanted to
> Op 28 aug 2008, om 08:54 heeft David Brownell het volgende geschreven:
> > p.s. FWIW my beagle identifies itself as 3430 ES2.2
> > not as 3530.
>
> You sadly can't detect the cpu revision in software (es2.2 doesn't
> exist for 3530 afaik), see the threads on linux-omap about
> adding that
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Gupta, Ramesh
> Sent: Wednesday, August 27, 2008 8:05 PM
> To: Dasgupta, Romit; Nayak, Rajendra; linux-omap@vger.kernel.org
> Subject: RE: [PATCH 00/01] CPUFreq: OMAP3 cpufreq driver
>
> Hi Romit,
>
> On Wed, Aug 27, 2008 at 9:38 AM, Felipe Balbi
> <[EMAIL PROTECTED]> wrote:
> > On Wed, Aug 27, 2008 at 09:26:34AM -0400, ext Ashwin Bihari wrote:
> >> Greetings,
> >>
> >> I'm trying to test out the MUSB support on my OMAP-3530 based device
> >> with the TWL4030 Phy. I'm using 2.6.22.18 and have
> Greetings,
>
> I'm trying to test out the MUSB support on my OMAP-3530 based device
> with the TWL4030 Phy. I'm using 2.6.22.18 and have tried to enable all
> different settings related to MUSB and nothing seems to happen. The
> TWL4030_USB driver builds and loads and claims that a cable is plugg
> Hi,
> I was wondering if any support has been added for the OMAP
> 35x processors?
>
> Can I at a minimum run a linux kernel with the console
> working? I have a TI Zoom OMAP35x Development board and
> wanted to get the git linux running on it.
Yes you can. Use the omap_ldp_defconfig to get
> > >
> > > These should be sent via linux-usb list, please also Cc
> > > linux-omap list.
> > >
> > > Thanks,
> > >
> > > Tony
> >
> >
> > Er Tony, the bus glue for OMAP is not present upstream. This patch fixes
> > something in that bus glue code, which currently exists only in your tree.
From: Anand Gadiyar <[EMAIL PROTECTED]>
If Indexed Mode register accesses are enabled, the ep0_rxstate()
function calls musb_g_ep0_giveback() before writing to the CSR
register. When control returns to this ep0_rxstate, the index
register contents are over-written. This causes the CSR register
wri
> -Original Message-
> From: [EMAIL PROTECTED] On Behalf Of Tony Lindgren
> * Pandita, Vikram <[EMAIL PROTECTED]> [080630 17:03]:
> >
> >
> >Code changes for final rev of EHCI/OHCI USB expansion board
> > 750-2099-001(C)
> >with h/w bug fixes to support ISP1504 PHY in input clockin
MUSB: Workaround for simultaneous TX and RX usage
MUSB RTL V1.4 has a hardware issue which results in a DMA controller
hang when TX and RX DMA channels are simultaneously enabled. This
affects at least OMAP2430 and OMAP34XX.
Since RX transfers are in Mode 0 and anyway result in one DMA interrupt
> On Mon, Aug 04, 2008 at 06:48:22PM +0530, ext Gadiyar, Anand wrote:
> > MUSB RTL v1.4 has a hardware issue which results in a DMA controller
> > hang when TX and RX DMA channels are simultaneously enabled. This
> > affects at least OMAP2430 and OMAP34XX.
> >
> >
> Hi All,
>
> If I have a USB camera with good Linux support, can I connect it
> to omap3evm(or any omap2) and make it functional?
I don't see why not. Do you expect a problem with using it? You could
use MUSB in host or OTG mode and connect the camera to the MUSB port.
- Anand--
To unsubscribe
> >> Actually, I'm still struggling in a bug similar with this one on Blackfin.
> >> We ran following testcase 100 times, 10-20 times tastcases failed.
> >>
> >> ---
> >> $ ./testusb -D /proc/bus/usb/005/012 -t14 -c 15000 -s 256 -v 1
> >> unknown speed /proc/bus/usb/005/012
> >> /proc/bus/usb/005
> > Also increase MUSB_LOGLEVEL to 3 in your .config file and reabuild that
> > 2.6.22.18 kernel.
> >
Don't bother re-building the kernel. You could just do an
"echo D3 > /proc/driver/musb_hdrc"
or even D5 for more detail. If low-level debug is not enabled, you can
"echo 8 > /pro
> On Tue, Aug 5, 2008 at 11:48 PM, Gadiyar, Anand <[EMAIL PROTECTED]> wrote:
> > From: Anand Gadiyar <[EMAIL PROTECTED]>
> >
> > If Indexed Mode register accesses are enabled, the ep0_rxstate() function
> > calls
> > musb_g_ep0_giveback() bef
> Hi all,
>
> I've pushed all the patches I have in my omap inbox, except for
> the omap serial driver that I want to look more.
>
> I've tried to comment on the ones that did not get pushed, then
> erased everything from my omap inbox. Some drivers should get
> integrated via other mailing lists,
From: Anand Gadiyar <[EMAIL PROTECTED]>
If Indexed Mode register accesses are enabled, the ep0_rxstate() function calls
musb_g_ep0_giveback() before writing to the CSR register. When control returns
to this ep0_rxstate, the index register contents are over-written. This causes
the CSR register wri
> Hi,
>
> * Bryan Wu <[EMAIL PROTECTED]> [080805 06:27]:
> > Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
> > ---
> > drivers/usb/musb/musb_gadget_ep0.c | 24
> > 1 files changed, 12 insertions(+), 12 deletions(-)
>
> I think all musb patches should be now posted to linux
> On Mon, Aug 04, 2008 at 06:48:22PM +0530, ext Gadiyar, Anand wrote:
> > MUSB RTL v1.4 has a hardware issue which results in a DMA controller
> > hang when TX and RX DMA channels are simultaneously enabled. This
> > affects at least OMAP2430 and OMAP34XX.
> >
> >
MUSB RTL v1.4 has a hardware issue which results in a DMA controller
hang when TX and RX DMA channels are simultaneously enabled. This
affects at least OMAP2430 and OMAP34XX.
Since RX transfers are in Mode 0 and anyway result in one DMA interrupt
per packet, we can use System DMA to unload the RX
Hi all,
With "no_hz=off" added to my bootargs, I get the following message every two
minutes
on my 3430SDP. Also seen on the beagleboard (with a different gpio number, I
think).
Has anyone seen this before? Any clues why this happens?
- Anand
(Sent the last mail without a subject. Sorry bout
Hi all,
With "no_hz=off" added to my bootargs, I get the following message every two
minutes
on my 3430SDP. Also seen on the beagleboard (with a different gpio number, I
think).
Has anyone seen this before? Any clues why this happens?
- Anand
<3>INFO: task twl4030 gpio:263 blocked for more th
> On Wed, 2008-07-30 at 21:56 +0530, ext Gadiyar, Anand wrote:
>
> > > Grr. Saying one needs to upgrade to the latest kernel before one can
> > > expect
> > > support is a bit like certain proprietary OS vendors - and even they do a
> > > better
> >
> On Wed, Jul 30, 2008 at 09:53:43PM +0530, ext Gadiyar, Anand wrote:
> > Grr. Saying one needs to upgrade to the latest kernel before one can expect
> > support is a bit like certain proprietary OS vendors - and even they do a
> > better
> > job than this.
>
&
>> On Wed, Jul 30, 2008 at 07:21:53AM -0700, ext Emanoil Kotsev wrote:
>> >
>> > Dear Felipe, I just want to tell, that while still developing kernels in
>> > the 2.6.2X
>> series a kernel 2.6.22 can not be labeled as old. Besides it comes along
>> with few
>> distros as default kernel.
>> >
>> >
> On Wed, Jul 30, 2008 at 07:21:53AM -0700, ext Emanoil Kotsev wrote:
> >
> > Dear Felipe, I just want to tell, that while still developing kernels in
> > the 2.6.2X
> series a kernel 2.6.22 can not be labeled as old. Besides it comes along with
> few
> distros as default kernel.
> >
> > A lot of
> 2008/7/29 Felipe Balbi <[EMAIL PROTECTED]>:
>> On Tue, Jul 29, 2008 at 02:07:51PM -0500, Woodruff, Richard wrote:
>>> > How about renaming it to twl92230c before submitting upstream? As far
>>> > as I can tell the name menelaus appears only in linux and makes it
>>> > hard to associate with the
> Hi All
> I have a omap3430 logic zoom board.
> I want to configure bluetooth on it(BRF6300) which will
> interfaced to UART2.
> I gone through the schematics and could find that the BT_SHUTDOWN is
> controlled through GPIO.8 coming from TWL4030.
> Is that wright? I tried using that GPIO but the h
> >> diff --git a/arch/arm/mach-omap2/pm34xx.c
> >> b/arch/arm/mach-omap2/pm34xx.c
> >> index 202c269..308835b 100644
> >> --- a/arch/arm/mach-omap2/pm34xx.c
> >> +++ b/arch/arm/mach-omap2/pm34xx.c
> >> @@ -380,11 +380,11 @@ int __init omap3_pm_init(void)
> >>goto err1;
> >>
Hi,
> Hi,
>
> "ext Gadiyar, Anand" <[EMAIL PROTECTED]> writes:
>
> > Hi All,
> >
> >
> >
> >> > > Tried that and I get the same hang, so I don't think the RTC is to
> >> > > blame.
> >> >
&
Hi All,
> > > Tried that and I get the same hang, so I don't think the RTC is to blame.
> >
> > Short update just in case anybody has an idea:
> >
> > Gadiyar spent some time with git-bisect (thanks!):
> >
> > It seems that the bad commit is probably between:
> > # good: [3ffec4e18484c34838fa34
> -Original Message-
> From: Dirk Behme [mailto:[EMAIL PROTECTED]
> Sent: Saturday, July 05, 2008 12:56 PM
> To: linux-omap@vger.kernel.org
> Cc: Gadiyar, Anand
> Subject: Re: Kernel hang on OMAP3 based Beagle board, RTC issue?
>
> Koen Kooi wrote:
> >
>
> * [EMAIL PROTECTED] <[EMAIL PROTECTED]> [080702 15:25]:
> > From: Iqbal Shareef <[EMAIL PROTECTED]>
> >
> > Separate out 3430 LCD panel support from 2430 SDP.
> >
> > Currently the support for the LCD on 3430SDP is added in
> the lcd_2430sdp.c
> > file. This patch separates it out to a new file.
> At Beagle IRC there was some discussion [1] [2] today about kernel
> hang on OMAP3 based Beagle board. I'll try to summarize discussion and
> Khasim's findings, maybe somebody here has an idea.
>
> Latest OMAP git kernel seems to hang on beagle board after some time.
> You don't see any crash, bu
> Actually, I don't have any detail information about the IP from mentor of
> Blackfin.
> I just found the instruction from the Blackfin manual. We need to clear DMA
> IRQ flag
> manually on Blackfin, although it is not true on Davinci.
>
> >
> >> > > But when I tried to write large file to the
> > That wasn't what I said or meant. What I did want to bring out was that
> > having
> > something built-in might give it more exposure to test by someone who wasn't
> > actively working on that area. And most bugs are caught by people other than
> > the active developers.
>
> Not really, anothe
> > My main bone of contention was the statement that there was no reason for
> > not building something as a module. There is a case for building drivers
> > into the kernel. Whether it is the best choice is something that depends
> > on what one is trying to achieve.
>
> As Felipe wrote, it is ea
> > And like you said, if the defconfig is all modular (or all built-in)
> > the user/manufacturer/hacker can always change it later. Although
> > I defend that Reference Boards' defconfigs should be as modular
> > as possible.
>
> I totally agree: furthermore testing power features is damn easier
> > Current omap hsmmc driver is not pm friendly. Build it as a module
> > because it prevents omap3 retention.
>
> Small comment.
>
> At least this patch shouldn't be reverted, there's no reason
> for not building drivers as modules. I'll do the same
> to musb.
Actually there is. It really depend
> > > Fix hdrc_cnf.h for omap3 configuration.
> >
> > Does this break the configuration for omap2?
> >
> > We should set these dynamically if different for omap2 and omap3
> > so we can compile both into the same kernel.
>
> Should check omap2430 trm to be sure, maybe someone in TI
> could help us
> > Hi all,
> >
> > Commit 5b36d70fa08f09de161487fe7f6e04200ffb8d71 breaks boot on OMAP3430
> > SDP. Reversing the patch allows the boot to work.
> >
> > Bootlog and the patch are shown below.
> >
> > Regards,
> > Anand
> >
> >
> >
> > commit 5b36d7
Hi all,
Commit 5b36d70fa08f09de161487fe7f6e04200ffb8d71 breaks boot on OMAP3430 SDP.
Reversing the patch allows the boot to work.
Bootlog and the patch are shown below.
Regards,
Anand
commit 5b36d70fa08f09de161487fe7f6e04200ffb8d71
Author: Joun
> > Separate out 3430 LCD panel support from 2430 SDP.
> >
> > Currently the support for the LCD on 3430SDP is added in the lcd_2430sdp.c
> > file. This patch separates it out to a new file.
>
> You're at least missing 3430sdp defconfig updates, Kconfig changes
> in drivers/media/video/omap and the
> FYI,
>
> someone put the full linux history in only one git repository
>
> http://marc.info/?l=linux-kernel&m=121276799115541&w=2
Awesome. Thanks for the link.
- Anand
>
> --
> Best Regards,
>
> Felipe Balbi
> [EMAIL PROTECTED]
> http://blog.felipebalbi.com
--
To unsubscribe from this list: se
> Hi folks,
>
> I am trying to enable the whole musb HS DMA code on Blackfin. But
> found the is no place to clean the DMA interrupt flag in musbhsdma.c.
> As a result, the irq always happens with the same DMA irq source. I
> add some code to clear the DMA interrupt. Did I miss something here?
The
> +
> +static struct omap_mcbsp_platform_data omap2_mcbsp_pdata[] = {
> +#ifdef CONFIG_ARCH_OMAP24XX
> + {
> + .virt_base = IO_ADDRESS(OMAP24XX_MCBSP1_BASE),
> + .dma_rx_sync= OMAP24XX_DMA_MCBSP1_RX,
> + .dma_tx_sync= OMAP24XX_DMA_MCBSP1_
Hi,
I am unable to visit any of these links. I get the following error "Unknown or
invalid plugin: 'tracker'".
Regards,
Anand
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Bryan Wu
> Sent: Saturday, May 17, 2008 4:31 PM
> To: [EMAIL PROTECTED];
> * Gadiyar, Anand <[EMAIL PROTECTED]> [080512 06:01]:
> > Hi Tony,
> >
> > I was trying to look at the history of the following file in gitweb:
> >
> >
> > It throws a parsing error seemingly because of characters
> in the above
> >
Hi Tony,
I was trying to look at the history of the following file in gitweb:
It throws a parsing error seemingly because of characters in the above
commit's Author field.
Any chance we can fix this? (I'm not even sure if we should, but if Luis
doesn't mind, maybe we could change it to
> Hi all,
>
> Here are three patches to clean DMA code to support multi-boot
> better. I have made quick testing on 24xx and 34xx only so far,
> and things seem to work.
>
> I will also do more testing, but I would appreciate if people would
> give them a quick spin and see if anything breaks. Func
> Hi all,
>
> Here are three patches to clean DMA code to support multi-boot
> better. I have made quick testing on 24xx and 34xx only so far,
> and things seem to work.
>
> I will also do more testing, but I would appreciate if people would
> give them a quick spin and see if anything breaks. Func
> -Original Message-
> From: Tony Lindgren [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 25, 2008 10:16 PM
> To: Gadiyar, Anand
> Cc: Eduardo Valentin; linux-omap@vger.kernel.org; Eduardo Valentin
> Subject: Re: [PATCH 4/5] OMAP3xx: Add DMA and IRQ definition
&
> >
> >
> > > diff --git a/include/asm-arm/arch-omap/dma.h
> > > b/include/asm-arm/arch-omap/dma.h
> > > index be0431e..270e158 100644
> > > --- a/include/asm-arm/arch-omap/dma.h
> > > +++ b/include/asm-arm/arch-omap/dma.h
> > > @@ -273,6 +273,10 @@
> > > #define OMAP24XX_DMA_MS
> diff --git a/include/asm-arm/arch-omap/dma.h
> b/include/asm-arm/arch-omap/dma.h
> index be0431e..270e158 100644
> --- a/include/asm-arm/arch-omap/dma.h
> +++ b/include/asm-arm/arch-omap/dma.h
> @@ -273,6 +273,10 @@
> #define OMAP24XX_DMA_MS 63 /* S_DMA_62 */
> #defin
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Felipe Balbi
> Sent: Thursday, April 24, 2008 7:16 PM
> To: linux-omap@vger.kernel.org; David Brownell
> Cc: Tony Lindgren; Syed Mohammed, Khasim; Felipe Balbi
> Subject: [PATCH 2/2] USB: Generalize usb
> > From: Anand Gadiyar <[EMAIL PROTECTED]>
> >
> > Updates to the hdrc_cnf.h file to enable the full range of
> 16 endpoints.
> > This patch fixes the "musb_hdrc: invalid ep 8" messages
> that show up on boot.
>
> Still doesn't fix:
>
> * This file contains configuration constants for the (m
From: Anand Gadiyar <[EMAIL PROTECTED]>
Updates to the hdrc_cnf.h file to enable the full range of 16 endpoints.
This patch fixes the "musb_hdrc: invalid ep 8" messages that show up on boot.
Signed-off-by: Paul Walmsley <[EMAIL PROTECTED]>
Signed-off-by: Anand Gadiyar <[EMAIL PROTECTED]>
Signed-o
Nice job! :)
By the way, how did you manage to get a list of checkpatch ERRORS and WARNINGS
on a set of files?
Did you do a compare with /dev/null or is there a better way?
Regards,
Anand
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Felipe Bal
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Felipe Balbi
> Sent: Friday, April 11, 2008 1:58 PM
> To: linux-omap@vger.kernel.org
> Cc: Felipe Balbi
> Subject: [PATCH 01/23] I2C: TWL4030: checkpatch.pl fixes for
> twl4030-core.c
>
> Misc cleanup
> > > driver is limited to 8 endpoints by macros in hdrc_cnf.h.
> > >
> > > Anyway, I don't know much about MUSB. David or Felipe, maybe you could
> > > take a quick look at this patch?
> >
> > I had this same patch queued for sending but i was waiting until i finished
> > a whole series for mus
> Sent: Tuesday, April 08, 2008 8:13 PM
> To: Gadiyar, Anand
> Cc: linux-omap@vger.kernel.org
> Subject: OMAP2430 build breakage
>
> Hi Anand,
>
> Regarding the building of omap_2430sdp_defconfig and
> omap_2430osk_defconfig, I'm going to send today a new - and comple
Hi all,
omap_2430sdp_defconfig and omap_2430osk_defconfig builds seem to be broken.
(also reported at [1])
I tried to use git bisect to narrow down the exact patch that caused this and
it looks like some patches that got merged don't compile individually. This
causes the git bisect process to
From: Anand Gadiyar <[EMAIL PROTECTED]>
The end address for the USB memory resources were incorrectly defined as
( + ) instead of ( + ) resulting in a
potential overlap with the start address of other resources.
Signed-off-by: Anand Gadiyar <[EMAIL PROTECTED]>
Acked-by: Nishant Kamat <[EMAIL PROT
>
> I'm still unable to clone the git tree from the mvista site.
>
> I use "git clone http://source.mvista.com/gittrees/linux-omap-2.6.git";
>
> I can't use the git://* URLs either. I'm behind a proxy and exporting
> http_proxy isn't helping.
>
Was finally able to clone from kernel.org. Fou
Hi all,
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Hilman
> Sent: Friday, April 04, 2008 11:46 PM
> To: Tony Lindgren
> Cc: Iqbal; linux-omap@vger.kernel.org
> Subject: Re: source.mvista links are broken
>
> Tony Lindgren <[EMAIL PROTEC
From: Anand Gadiyar <[EMAIL PROTECTED]>
This patch changes the return value of omap_dma_chain_a_transfer
to 0 on success instead of the flag 'start_dma', which wasn't really useful
for anything.
Signed-off-by: Anand Gadiyar <[EMAIL PROTECTED]>
---
This patch seems to have been accidentally revers
Ack. Meant to send in this fix this weekend.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Hilman
> Sent: Saturday, March 08, 2008 3:19 AM
> To: linux-omap@vger.kernel.org
> Cc: Kevin Hilman
> Subject: [PATCH] ARM: OMAP: DMA: fix CLINK mask
301 - 397 of 397 matches
Mail list logo
