SEARCH  

NEWS

2010.10.06:11:36:28
Komputronik: rośnie rola usług na rynku salonów komputerowych
Polski rynek salonów komputerowych zmienia swój charakter z typowo sprzedażowego na usługowy. W ten sposób salony wchodzą w wysokomarżowy segment gospodarki, który zajmowany był do tej pory przez wyspecjalizowane firmy. Jednocześnie zyskują nowe atuty w konkurencji z dużymi marketami elektronicznymi.

 

184722584522_575260007431Rob 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

 
148229314135_531860007462Rob 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

 
176225374999_599860007585Harikrishna 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 +

 
192424994340_599560007535Harikrishna 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

 
101427154309_517960007899Valentin 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

 
151523934157_503660007657Valentin 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

 
146826284588_560460007894Paulius 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.

 
106627074431_506460007158Paulius 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.

 
165026284658_599160007500Russell 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

 
152526384214_583460007762Russell 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

 
173323314155_589060007301Russell 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

 
154728374929_513460007874Russell 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

 
102825074581_545960007285luan 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:

 
161822204913_527560007536luan 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:

 
177627364173_599160007991Grant 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

 
175323034321_590860007690Grant 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

 
120827404527_513760007968Robert 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

 
101129034474_559260007045Robert 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

 
187729814266_579060007477Robert 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

 
132520314213_549860007783Robert 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

 
148827754086_581060007279Robert 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

 
150028914018_502660007894Robert 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

 
199520394796_546860007158Grant 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

 
151425074138_578060007394Grant 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

 
125626214425_546960007447David 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

 
125226074221_533860007904David 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

 
161829174795_563760007823David 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

 
153029384862_532660007492David 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

 
148429205000_562260007295Grant 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

 
101629564917_544260007035Grant 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

 
188926774643_511060007059Benjamin 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

 
101426334977_580960007920Benjamin 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

 
163128004858_549360007264Mark 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

 
198626094183_598560007883Mark 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

 
128022484839_519760007263Mark 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

 
123325784940_587660007956Mark 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

 
193627034589_591360007859Wolfgang 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

 
183221434658_569060007784Wolfgang 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

 
195426224393_513760007625Robert 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 -------------------------------------------------

 
101928864873_585860007562Robert 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 -------------------------------------------------

 
112123164140_506060007830Robert 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

 
101621274532_560560007044Grant 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

 
146428724187_512260007824Grant 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

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

 
192426724937_579660007019Alexander 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

 
135826514336_549960007527Scott 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

 
132827284655_586160007694Grant 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.

 
190527974566_509260007127Jon 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

 
191628254642_536060007293JeanChristophe 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

 
141120474966_534860007495JeanChristophe 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