Hi Pawel,
Sorry for the late reply, I'm currently attending LinuxCon Japan, my mail
backlog is growing.
On Tuesday 28 May 2013 11:52:52 Pawel Moll wrote:
> On Mon, 2013-05-27 at 11:31 +0100, Arnd Bergmann wrote:
> > On Monday 27 May 2013, Daniel Tang wrote:
> > > > The one remaining bit that
Hi Pawel,
Sorry for the late reply, I'm currently attending LinuxCon Japan, my mail
backlog is growing.
On Tuesday 28 May 2013 11:52:52 Pawel Moll wrote:
On Mon, 2013-05-27 at 11:31 +0100, Arnd Bergmann wrote:
On Monday 27 May 2013, Daniel Tang wrote:
The one remaining bit that sticks
On Wednesday 29 May 2013, Daniel Tang wrote:
> On 27/05/2013, at 8:31 PM, Arnd Bergmann wrote:
>
> > On Monday 27 May 2013, Daniel Tang wrote:
> >>> The one remaining bit that sticks out is the clcd platform data. As I
> >>> said before, I won't require you to convert that to DT in order to
>
On Wednesday 29 May 2013, Daniel Tang wrote:
On 27/05/2013, at 8:31 PM, Arnd Bergmann a...@arndb.de wrote:
On Monday 27 May 2013, Daniel Tang wrote:
The one remaining bit that sticks out is the clcd platform data. As I
said before, I won't require you to convert that to DT in order to
On 27/05/2013, at 8:31 PM, Arnd Bergmann wrote:
> On Monday 27 May 2013, Daniel Tang wrote:
>>> The one remaining bit that sticks out is the clcd platform data. As I
>>> said before, I won't require you to convert that to DT in order to
>>> get your code merged, but I'd also really like to see
On Tue, May 28, 2013 at 5:52 PM, Arnd Bergmann wrote:
> depends on KMS_ARMCLCD != 'y'
> depends on 'm' if KMS_ARMCLCD
Those two above could be one actually.
Just my 2 cents.
--
With Best Regards,
Andy Shevchenko
--
To unsubscribe from this list: send the line "unsubscribe
On Tuesday 28 May 2013 15:21:04 Pawel Moll wrote:
> On Tue, 2013-05-28 at 15:16 +0100, Linus Walleij wrote:
> > On Tue, May 28, 2013 at 12:54 PM, Pawel Moll wrote:
> > > On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote:
> > >> b) add a new KMS driver for this hardware that can be used as an
On Tue, 2013-05-28 at 15:16 +0100, Linus Walleij wrote:
> On Tue, May 28, 2013 at 12:54 PM, Pawel Moll wrote:
> > On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote:
> >> b) add a new KMS driver for this hardware that can be used as an
> >> alternative to the existing one and that works with
On Tue, May 28, 2013 at 12:54 PM, Pawel Moll wrote:
> On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote:
>> b) add a new KMS driver for this hardware that can be used as an
>> alternative to the existing one and that works with DT.
>
> There are people working on this, just trying to jump
On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote:
> b) add a new KMS driver for this hardware that can be used as an
> alternative to the existing one and that works with DT.
There are people working on this, just trying to jump through some legal
hoops to post a RFC. Once this is done
On Mon, 2013-05-27 at 11:31 +0100, Arnd Bergmann wrote:
> On Monday 27 May 2013, Daniel Tang wrote:
> > > The one remaining bit that sticks out is the clcd platform data. As I
> > > said before, I won't require you to convert that to DT in order to
> > > get your code merged, but I'd also really
On 27/05/2013, at 8:31 PM, Arnd Bergmann a...@arndb.de wrote:
On Monday 27 May 2013, Daniel Tang wrote:
The one remaining bit that sticks out is the clcd platform data. As I
said before, I won't require you to convert that to DT in order to
get your code merged, but I'd also really like to
On Mon, 2013-05-27 at 11:31 +0100, Arnd Bergmann wrote:
On Monday 27 May 2013, Daniel Tang wrote:
The one remaining bit that sticks out is the clcd platform data. As I
said before, I won't require you to convert that to DT in order to
get your code merged, but I'd also really like to see
On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote:
b) add a new KMS driver for this hardware that can be used as an
alternative to the existing one and that works with DT.
There are people working on this, just trying to jump through some legal
hoops to post a RFC. Once this is done we'll
On Tue, May 28, 2013 at 12:54 PM, Pawel Moll pawel.m...@arm.com wrote:
On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote:
b) add a new KMS driver for this hardware that can be used as an
alternative to the existing one and that works with DT.
There are people working on this, just trying
On Tue, 2013-05-28 at 15:16 +0100, Linus Walleij wrote:
On Tue, May 28, 2013 at 12:54 PM, Pawel Moll pawel.m...@arm.com wrote:
On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote:
b) add a new KMS driver for this hardware that can be used as an
alternative to the existing one and that
On Tuesday 28 May 2013 15:21:04 Pawel Moll wrote:
On Tue, 2013-05-28 at 15:16 +0100, Linus Walleij wrote:
On Tue, May 28, 2013 at 12:54 PM, Pawel Moll pawel.m...@arm.com wrote:
On Mon, 2013-05-27 at 11:32 +0100, Arnd Bergmann wrote:
b) add a new KMS driver for this hardware that can be
On Tue, May 28, 2013 at 5:52 PM, Arnd Bergmann a...@arndb.de wrote:
depends on KMS_ARMCLCD != 'y'
depends on 'm' if KMS_ARMCLCD
Those two above could be one actually.
Just my 2 cents.
--
With Best Regards,
Andy Shevchenko
--
To unsubscribe from this list: send the line
On Monday 27 May 2013, Daniel Tang wrote:
> > On Saturday 25 May 2013, Daniel Tang wrote:
> > The one remaining bit that sticks out is the clcd platform data. As I
> > said before, I won't require you to convert that to DT in order to
> > get your code merged, but I'd also really like to see that
On Monday 27 May 2013, Daniel Tang wrote:
> > The one remaining bit that sticks out is the clcd platform data. As I
> > said before, I won't require you to convert that to DT in order to
> > get your code merged, but I'd also really like to see that happen,
> > as we will also need that to get rid
On Monday 27 May 2013, Daniel Tang wrote:
The one remaining bit that sticks out is the clcd platform data. As I
said before, I won't require you to convert that to DT in order to
get your code merged, but I'd also really like to see that happen,
as we will also need that to get rid of
On Monday 27 May 2013, Daniel Tang wrote:
On Saturday 25 May 2013, Daniel Tang wrote:
The one remaining bit that sticks out is the clcd platform data. As I
said before, I won't require you to convert that to DT in order to
get your code merged, but I'd also really like to see that happen,
On 27/05/2013, at 7:23 AM, Arnd Bergmann wrote:
> On Saturday 25 May 2013, Daniel Tang wrote:
>> Changes between v3 and v4:
>> * Remove redundant clock-names in device tree
>> * Re-enable bus access to some peripherals on bootup
>> * Clean up nspire-classic-timer code.
>> - Implement a
On Saturday 25 May 2013, Daniel Tang wrote:
> Changes between v3 and v4:
> * Remove redundant clock-names in device tree
> * Re-enable bus access to some peripherals on bootup
> * Clean up nspire-classic-timer code.
> - Implement a nspire_timer_set_mode function
> - Removed messy IO_MATCHx and
On Saturday 25 May 2013, Daniel Tang wrote:
Changes between v3 and v4:
* Remove redundant clock-names in device tree
* Re-enable bus access to some peripherals on bootup
* Clean up nspire-classic-timer code.
- Implement a nspire_timer_set_mode function
- Removed messy IO_MATCHx and
On 27/05/2013, at 7:23 AM, Arnd Bergmann a...@arndb.de wrote:
On Saturday 25 May 2013, Daniel Tang wrote:
Changes between v3 and v4:
* Remove redundant clock-names in device tree
* Re-enable bus access to some peripherals on bootup
* Clean up nspire-classic-timer code.
- Implement a
Changes between
http://archive.arm.linux.org.uk/lurker/message/20130408.113343.585af217.en.html
and v2:
* Added new drivers to support the irqchip and timers on older models.
* Added new device trees to support the other models.
Changes between v2 and v3:
* Clean up keypad driver
* Update
Changes between
http://archive.arm.linux.org.uk/lurker/message/20130408.113343.585af217.en.html
and v2:
* Added new drivers to support the irqchip and timers on older models.
* Added new device trees to support the other models.
Changes between v2 and v3:
* Clean up keypad driver
* Update
28 matches
Mail list logo
