SEARCH  

NEWS

2010.10.06:11:36:28
IE ma już mniej niż 50% rynku
Globalne statystyki StatCounter mówią, że udział IE w rynku przeglądarek spadł poniżej 50%. Najszybciej nowych użytkowników zdobywała przeglądarka Google Chrome. Zmiany są szczególnie widoczne w Europie, gdzie wprowadzono do Windowsa ekran wyboru przeglądarek.

 

198026004030_592960007825Rob 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

 
151722454118_550460007468Rob 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

 
100227244706_578860007662Harikrishna 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 +

 
163822084670_525560007067Harikrishna 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

 
132023304847_500960007832Valentin 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

 
135124974431_538160007813Valentin 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

 
120629434057_532460007925Paulius 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.

 
179324484648_549860007609Paulius 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.

 
116028744817_583060007943Russell 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

 
189824484272_574460007791Russell 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

 
157628094287_500660007712Russell 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

 
181923964655_587760007100Russell 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

 
180125144549_544860007784luan 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:

 
105721724658_587560007786luan 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:

 
181729004234_508960007692Grant 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

 
188022194500_516660007691Grant 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

 
187920444086_553360007808Robert 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

 
163427224322_518260007334Robert 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

 
196722274506_562460007509Robert 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

 
140929184408_564360007051Robert 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

 
133428874271_583560007496Robert 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

 
152529324541_561160007462Robert 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

 
141920974183_574160007353Grant 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

 
107522454581_558160007682Grant 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

 
108922784600_549860007607David 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

 
155022554494_582160007547David 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

 
131626144478_585860007943David 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

 
131926454040_550360007319David 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

 
185724614565_543760007434Grant 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

 
111921314713_572060007633Grant 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

 
132721794889_582160007978Benjamin 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

 
136723164591_584660007816Benjamin 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

 
178824934460_582860007846Mark 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

 
114728534306_571360007348Mark 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

 
114724104480_586060007109Mark 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

 
149324564289_538160007288Mark 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

 
135826444604_594960007778Wolfgang 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

 
176522774271_522560007267Wolfgang 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

 
107022514119_537760007410Robert 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 -------------------------------------------------

 
172621114820_520560007949Robert 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 -------------------------------------------------

 
131524634405_560460007682Robert 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

 
189222024326_549660007816Grant 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

 
127429164092_554560007197Grant 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

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

 
134123144524_516060007495Alexander 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

 
110928354958_551560007802Scott 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

 
119623304004_552360007155Grant 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.

 
133821004070_543160007211Jon 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

 
162824574423_507760007012JeanChristophe 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

 
149027304326_501460007846JeanChristophe 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