SEARCH  

NEWS

2010.10.06:11:36:28
Najpopularniejsze domeny dla Twojej firmy w nazwa.pl (reklama)
Myślisz o zdobyciu zagranicznych rynków? Chcesz mieć adresy WWW w najbardziej rozpoznawalnych domenach? A może chciałbyś zabezpieczyć swoją markę przed wykorzystaniem jej przez kogoś innego? Powinieneś więc rozważyć rejestrację firmowych adresów WWW zawierających najpopularniejsze rozszerzenia używane na świecie.

 

123921674391_527660007271Rob Emanuele
Hi Haavard, Id be happy to reintegrate my changes to this back into the Atmel driver once I get it working correct on the at91. Do you have the equipment to give my changes a try? Converting my #d

 
119328784720_566560007121Rob Emanuele
Rob Emanuele : Greetings, This patch creates a new AT91 Multimedia Card Interface (MCI) driver that supports using both MCI slots at the same time. Im looking for others to test this patc

 
186822064907_583860007414Harikrishna Donti
Signed-off-by: Michael Roth <mroth@xxxxxxxxx Cc: Nicolas Ferre <nicolas.ferre@xxxxxxxxx --- arch/arm/mach-at91/include/mach/board.h | 1 + drivers/mmc/host/at91_mci.c | 4 +

 
133421904489_536560007921Harikrishna Donti
Harikrishna Donti wrote: I have taken enough care in my driver not to call spi_sync() more than once at a time by a mutex lock. Still I dont understand why the overrun would occur. Im unfa

 
120429724362_548060007833Valentin Longchamp
Harikrishna Donti wrote: When I start an application which uses UART1-5 (i.e., data tx,rx in UART which also uses DMA) then I get SPI overrun errors. So, seems like there is some kind of DMA

 
182421314000_521460007351Valentin Longchamp
Harikrishna Donti wrote: When I start an application which uses UART1-5 (i.e., data tx,rx in UART which also uses DMA) then I get SPI overrun errors. So, seems like there is some kind of DMA

 
148526014228_520560007964Paulius Zaleckas
On Thu, May 28, 2009 at 04:46:21PM +0200, Valentin Longchamp wrote: changes since v1: we now check if the parent configuration bit was changed since reset and change the parent when needed.

 
132621334170_523360007134Paulius Zaleckas
On Thu, May 28, 2009 at 04:46:21PM +0200, Valentin Longchamp wrote: changes since v1: we now check if the parent configuration bit was changed since reset and change the parent when needed.

 
164723054325_513660007402Russell King ARM Li
On Thu, May 28, 2009 at 05:07:34PM +0300, Paulius Zaleckas wrote: Please pull the following minor fixes/changes (diff attached inline): This appears to have missed Linus pull of my tree, so Im goi

 
105628754374_541860007265Russell King ARM Li
On Thu, May 28, 2009 at 05:07:34PM +0300, Paulius Zaleckas wrote: Please pull the following minor fixes/changes (diff attached inline): This appears to have missed Linus pull of my tree, so Im goi

 
125121774397_525160007805Russell King ARM Li
Hi All, I have been trying to change the cache policy to write allocate for both user and kernel memory (i.e normal memory). I changed the cachepolicy variable in arch/arm/mm/mmu.c, but seems like

 
160228764406_583060007671Russell King ARM Li
Hi All, I have been trying to change the cache policy to write allocate for both user and kernel memory (i.e normal memory). I changed the cachepolicy variable in arch/arm/mm/mmu.c, but seems like

 
179424074805_596560007776luan dinh
----- Original Message ----- From: "Russell King - ARM Linux" <linux@xxxxxxxxxxxxxxxx Subject: Re: Cachepolicy question On Thu, May 28, 2009 at 06:46:31PM +0530, Hemanth V wrote:

 
109922874080_542460007751luan dinh
----- Original Message ----- From: "Russell King - ARM Linux" <linux@xxxxxxxxxxxxxxxx Subject: Re: Cachepolicy question On Thu, May 28, 2009 at 06:46:31PM +0530, Hemanth V wrote:

 
182724804625_520160007979Grant Likely
Hi, All Currently, ARM linux uses mach-type to figure out platform. But mach-type could not handle variants well and it doesnt tell the kernel about info about attached peripherals. The device-tree

 
146721494156_586460007547Grant Likely
Hi, All Currently, ARM linux uses mach-type to figure out platform. But mach-type could not handle variants well and it doesnt tell the kernel about info about attached peripherals. The device-tree

 
166920024423_507460007504Robert Schwebel
On Wed, May 27, 2009 at 9:27 AM, Grant Likely <grant.likely@xxxxxxxxxxxx wrote: Signed-off-by: janboe <yuan-bo.ye@xxxxxxxxxxxx Heeheehe, This is Fantastic. Yes, I agree. Thanks for

 
174626274912_555060007551Robert Schwebel
On Wed, May 27, 2009 at 9:27 AM, Grant Likely <grant.likely@xxxxxxxxxxxx wrote: Signed-off-by: janboe <yuan-bo.ye@xxxxxxxxxxxx Heeheehe, This is Fantastic. Yes, I agree. Thanks for

 
132526914839_540560007262Robert Schwebel
On Wed, May 27, 2009 at 9:05 AM, Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx wrote: Seriously: oftree in general is a good idea. Just that it doesnt work in practise. The concept has some seri

 
115629434743_578160007641Robert Schwebel
On Wed, May 27, 2009 at 9:05 AM, Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx wrote: Seriously: oftree in general is a good idea. Just that it doesnt work in practise. The concept has some seri

 
176026114791_591660007191Robert Schwebel
On Wed, May 27, 2009 at 10:20 AM, Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx wrote: That being said, the problems we have had are the reason why it is *not* recommended to hard link the dev

 
146221434194_588660007027Robert Schwebel
On Wed, May 27, 2009 at 10:20 AM, Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx wrote: That being said, the problems we have had are the reason why it is *not* recommended to hard link the dev

 
138929644654_530060007246Grant Likely
From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx Date: Thu, 28 May 2009 01:48:01 +0200 My impression is that oftree only works in a perfect world. But we dont have one, so the fundamental de

 
185228384937_569160007052Grant Likely
From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx Date: Thu, 28 May 2009 01:48:01 +0200 My impression is that oftree only works in a perfect world. But we dont have one, so the fundamental de

 
195323994996_569560007139David Miller
Robert Schwebel wrote: The oftree by design wants to be a complete hardware description. As you mention above, there are cases where you *nevertheless* need ad-hoc information about things *not

 
133629404750_512660007224David Miller
Robert Schwebel wrote: The oftree by design wants to be a complete hardware description. As you mention above, there are cases where you *nevertheless* need ad-hoc information about things *not

 
131723174368_551260007585David Miller
On Wed, May 27, 2009 at 06:58:24PM -0500, Scott Wood wrote: Robert Schwebel wrote: The oftree by design wants to be a complete hardware description. As you mention above, there are cases wher

 
153925924548_519260007061David Miller
On Wed, May 27, 2009 at 06:58:24PM -0500, Scott Wood wrote: Robert Schwebel wrote: The oftree by design wants to be a complete hardware description. As you mention above, there are cases wher

 
143927444900_537560007142Grant Likely
On Wed, May 27, 2009 at 05:15:25PM -0700, David Miller wrote: From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx It works badly for corner cases, and embedded land is full of it. The eff

 
142823874542_542360007722Grant Likely
On Wed, May 27, 2009 at 05:15:25PM -0700, David Miller wrote: From: Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx It works badly for corner cases, and embedded land is full of it. The eff

 
156324184661_531260007516Benjamin Herrenschmi
On Thu, May 28, 2009 at 04:32:40PM -0600, Grant Likely wrote: and half-assed example of this). However, when it comes to complex configurations that cannot be easily described, Im all for using

 
153728634834_590560007036Benjamin Herrenschmi
On Thu, May 28, 2009 at 04:32:40PM -0600, Grant Likely wrote: and half-assed example of this). However, when it comes to complex configurations that cannot be easily described, Im all for using

 
149029134629_503860007521Mark Brown
On Sat, May 30, 2009 at 07:52:46PM +1000, Benjamin Herrenschmidt wrote: Sure. My only big concern with it is that it compeltely sidesteps clocking decisions so theres a lot of codecs its

 
109925444265_599960007700Mark Brown
On Sat, May 30, 2009 at 07:52:46PM +1000, Benjamin Herrenschmidt wrote: Sure. My only big concern with it is that it compeltely sidesteps clocking decisions so theres a lot of codecs its

 
114123484087_568360007170Mark Brown
1. implementers of the clock API which have not been subject to my rigorous review abuse it to the point of making the API essentially useless, and that causes Mark problems. If thats a proble

 
140523344589_506560007133Mark Brown
1. implementers of the clock API which have not been subject to my rigorous review abuse it to the point of making the API essentially useless, and that causes Mark problems. If thats a proble

 
158221834997_541660007370Wolfgang Denk
On Wed, May 27, 2009 at 6:07 PM, Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx wrote: On Wed, May 27, 2009 at 06:58:24PM -0500, Scott Wood wrote: Robert Schwebel wrote: The oftree by design

 
145325784282_508160007388Wolfgang Denk
On Wed, May 27, 2009 at 6:07 PM, Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx wrote: On Wed, May 27, 2009 at 06:58:24PM -0500, Scott Wood wrote: Robert Schwebel wrote: The oftree by design

 
160327174933_586960007852Robert Schwebel
From: Wolfgang Denk <wd@xxxxxxx Date: Thu, 28 May 2009 11:51:26 +0200 Lost business. D*mn... [Maybe this explains Roberts reluctance?] ROFL -------------------------------------------------

 
156928574199_565660007971Robert Schwebel
From: Wolfgang Denk <wd@xxxxxxx Date: Thu, 28 May 2009 11:51:26 +0200 Lost business. D*mn... [Maybe this explains Roberts reluctance?] ROFL -------------------------------------------------

 
182729444304_541560007952Robert Schwebel
On Thu, May 28, 2009 at 6:13 AM, Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx wrote: On Thu, May 28, 2009 at 11:51:26AM +0200, Wolfgang Denk wrote: True. From a commercial point of view this i

 
154925924134_554560007223Grant Likely
On Thu, May 28, 2009 at 02:07:07AM +0200, Robert Schwebel wrote: On Wed, May 27, 2009 at 06:58:24PM -0500, Scott Wood wrote: Robert Schwebel wrote: The oftree by design wants to be a compl

 
191524614802_519760007418Grant Likely
Dear Robert Schwebel, In message <20090528000707.GR6805@xxxxxxxxxxxxxx you wrote: Until now, oftree has created more problems than it has solved for us. The idea works fine for well-known

 
158621454134_551860007850Alexander Clouter
-----Original Message----- From: devicetree-discuss-bounces+stephen.neuendorffer=xilinx.com@xxxxxxxxxx [ rel="nofollow" mailto:devicetree- mailto:devicetree- discuss-bounces+stephen.neuen

 
136925824706_556960007245Alexander Clouter
On Wed, May 27, 2009 at 12:56 PM, Alexander Clouter <alex@xxxxxxxxxxxxx wrote: In gmane.linux.kernel Grant Likely <grant.likely@xxxxxxxxxxxx wrote: On Wed, May 27, 2009 at 9:05 AM, Rober

 
153920644189_584460007199Scott Wood
"Robert" == Robert Schwebel <r.schwebel@xxxxxxxxxxxxxx writes: Hi, Robert - The whole concept is based on the assumption that bindings Robert are defined *once*, then never

 
179520284791_593060007799Grant Likely
On Wed, May 27, 2009 at 11:23:29AM -0500, Scott Wood wrote: That removes the ability to use the device tree to pass information from the bootloader, such as MAC addresses and clock frequencies.

 
115324894260_595560007803Jon Smirl
Russell King wrote: On Wed, May 27, 2009 at 11:23:29AM -0500, Scott Wood wrote: That removes the ability to use the device tree to pass information from the bootloader, such as MAC addresse

 
137222724949_550760007962JeanChristophe PLAGN
On Wed, May 27, 2009 at 03:13:55PM -0400, Jon Smirl wrote: On Wed, May 27, 2009 at 3:08 PM, Scott Wood <scottwood@xxxxxxxxxxxxx wrote: Im not talking about platform specific code, Im talkin

 
135621594544_506260007783JeanChristophe PLAGN
On Wed, May 27, 2009 at 1:39 PM, Jean-Christophe PLAGNIOL-VILLARD <plagnioj@xxxxxxxxxxxx wrote: On 20:21 Wed 27 May     , Russell King - ARM Linux wrote: On Wed, May 27, 2009 at 03

 

 

home   |    register   |    login