SEARCH  

NEWS

2010.10.06:11:36:28
Przez komiks i animację do wiedzy ekonomicznej
Komiksy, animacje i scenariusze lekcji, przygotowane przez metodyków z Ośrodka Rozwoju Edukacji we współpracy z ekonomistami Fundacji FOR, będą dystrybuowane bezpłatnie wśród nauczycieli szkół gimnazjalnych i ponadgimnazjalnych, prowadzących lekcje z podstaw przedsiębiorczości i wiedzy o społeczeństwie. Wspomniane materiały będą dostępne dla nauczycieli na stronie internetowej FOR.

 

154521714672_597060007371Rob 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

 
200021144168_598760007542Rob 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

 
115722414328_541260007499Harikrishna 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 +

 
109624224030_505460007472Harikrishna 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

 
107627444944_533560007172Valentin 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

 
168622774344_535860007215Valentin 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

 
172922464329_589860007830Paulius 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.

 
143923904070_576760007000Paulius 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.

 
126628994422_529660007819Russell 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

 
176820294563_571260007295Russell 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

 
188520514573_522860007820Russell 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

 
144321374066_577360007298Russell 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

 
160224734689_567260007490luan 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:

 
167325064388_509560007341luan 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:

 
191425714371_547760007736Grant 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

 
177221664788_534560007196Grant 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

 
116428384334_523060007368Robert 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

 
152922124842_521760007082Robert 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

 
170825574589_509660007391Robert 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

 
143725664963_580960007244Robert 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

 
154528154411_533260007806Robert 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

 
152823244644_586260007254Robert 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

 
123020824466_507260007351Grant 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

 
115520074908_574460007560Grant 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

 
113525414126_509760007169David 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

 
134228944985_575360007144David 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

 
155927544468_520260007022David 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

 
145628474105_592260007405David 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

 
127320744413_518160007517Grant 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

 
174129544057_586860007407Grant 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

 
103723924301_502160007527Benjamin 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

 
116527044281_563460007898Benjamin 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

 
165623624744_576260007663Mark 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

 
116625574738_557960007555Mark 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

 
109524784509_515360007559Mark 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

 
156123834952_586260007096Mark 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

 
138825704801_567060007706Wolfgang 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

 
156728614067_531060007351Wolfgang 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

 
197427894908_571160007645Robert 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 -------------------------------------------------

 
126624634123_577560007470Robert 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 -------------------------------------------------

 
133421774853_528560007257Robert 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

 
138224274828_518260007032Grant 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

 
188926634893_595660007514Grant 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

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

 
186129254133_598560007750Alexander 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

 
145420334928_530760007967Scott 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

 
156527004393_539260007490Grant 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.

 
142427714153_531760007127Jon 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

 
183120334074_513360007733JeanChristophe 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

 
180421094657_593860007356JeanChristophe 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