On Sun, 20 Jan 2013 06:05:58 + (UTC)
Nerdopolis wrote:
> Nerdopolis writes:
>
>
> > I see.
> > The only concern is that can the vesafb fbdev device resolution be changed
> > in
> > runtime if its too small?
No. See
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f
The fbdev backend is a welcome sight here and I've been trying it out on a
Nokia N900; in the minimal testing I've done so far (some input issues on the
touchpad and keyboard mean I couldn't test too much interactive usage) it works
well, so thanks.
However one issue I've found is that no input
Nerdopolis writes:
> I see.
> The only concern is that can the vesafb fbdev device resolution be changed in
> runtime if its too small?
> Otherwise users are going to have to manually set the framebuffer size by
> correcting the correct vga= argument with grub if they get the wrong size.
>
...
David Herrmann writes:
> I don't think this is a good idea. We have a vesafb in the kernel so
> please use this instead of accessing graphic-cards via VESA from
> user-space.
> I don't see any reason why we should copy vesafb-code into weston.
>
> vesafb provides a fbdev device which then can be
Hi
On Fri, Jan 18, 2013 at 6:54 PM, Bengt Richter wrote:
> Hi all,
>
> Can this fb compositor be run as non-root (but member of video group for
> access to /dev/fb?) ?
Yes.
> I run X as non-root user via a startx script. Could one hope for an
> analogous startw script that
> puts one in a shell
Hi
On Sat, Jan 19, 2013 at 7:12 PM, nerdopolis
wrote:
> Hi.
>
>
>
> I tried experimenting with the latest fbdev-backend on my Live CD on an old
> Intel laptop and it seems to work pretty good.
>
>
>
> However I did run into a few problems with VirtualBox which isn't really the
> fault of fbdev-ba
Hi.
I tried experimenting with the latest fbdev-backend on my Live CD on an old
Intel laptop and it seems to work pretty good.
However I did run into a few problems with VirtualBox which isn't really the
fault of fbdev-backend, but problems that prevented it from working.
I tried to use Weston
On 01/18/2013 01:01 PM Philip Withnall wrote:
On Fri, 2013-01-18 at 13:09 +0200, Pekka Paalanen wrote:
Why not discover that device via udev? That would avoid any hard-coded
paths. And you could do an fbdev_output_create() on all fbdev devices
you find.
Good idea. It's not on my list of priori
On Fri, 2013-01-18 at 13:09 +0200, Pekka Paalanen wrote:
> > > Why not discover that device via udev? That would avoid any hard-coded
> > > paths. And you could do an fbdev_output_create() on all fbdev devices
> > > you find.
> >
> > Good idea. It's not on my list of priorities though, since I (co
On Fri, 18 Jan 2013 10:45:27 +
Philip Withnall wrote:
> Hi David,
>
> Thanks for the review. Replies inline, and a new patch coming up soon.
>
> On Wed, 2013-01-16 at 21:22 +0100, David Herrmann wrote:
> > Hi Philip
> >
> > I like the simple design of this. I don't think we need to share m
On Wed, 2013-01-16 at 12:02 +0200, Pekka Paalanen wrote:
> What do you have in mind for polishing? If it is the evdev and VT code
> sharing between several backends, you will find that the android
> backend will make it not so nice. IMO we could merge fbdev backend, and
> refactor code later.
I mo
Hi David,
Thanks for the review. Replies inline, and a new patch coming up soon.
On Wed, 2013-01-16 at 21:22 +0100, David Herrmann wrote:
> Hi Philip
>
> I like the simple design of this. I don't think we need to share much
> of the code as it's pretty simple.
>
> I haven't checked all of it, b
On Wed, Jan 16, 2013 at 11:22 PM, David Herrmann
wrote:
> Hi Philip
>
> I like the simple design of this. I don't think we need to share much
> of the code as it's pretty simple.
>
> I haven't checked all of it, but some comments below.
>
> Thanks
> David
>
> On Tue, Jan 15, 2013 at 3:08 PM, Phili
Hi Philip
I like the simple design of this. I don't think we need to share much
of the code as it's pretty simple.
I haven't checked all of it, but some comments below.
Thanks
David
On Tue, Jan 15, 2013 at 3:08 PM, Philip Withnall wrote:
> This is an initial version of an fbdev backend for Wes
On Tue, 15 Jan 2013 14:08:10 +
Philip Withnall wrote:
> This is an initial version of an fbdev backend for Weston. I don't
> consider it polished; I'm just looking for rough feedback at the
> moment. The work is also available as a gitorious branch if anyone
> prefers that:
> https://gitoriou
Hi Vasily
On Tue, Jan 15, 2013 at 4:13 PM, Vasily Khoruzhick wrote:
> On Tue, Jan 15, 2013 at 5:08 PM, Philip Withnall
> wrote:
>> This is an initial version of an fbdev backend for Weston. I don't
>> consider it polished; I'm just looking for rough feedback at the
>> moment. The work is also a
On Tue, Jan 15, 2013 at 5:08 PM, Philip Withnall wrote:
> This is an initial version of an fbdev backend for Weston. I don't
> consider it polished; I'm just looking for rough feedback at the
> moment. The work is also available as a gitorious branch if anyone
> prefers that:
> https://gitorious.o
This is an initial version of an fbdev backend for Weston. I don't
consider it polished; I'm just looking for rough feedback at the
moment. The work is also available as a gitorious branch if anyone
prefers that:
https://gitorious.org/~pwithnall/weston/pwithnalls-weston/commits/compositor-fbdev
On
18 matches
Mail list logo
