From: Bernd Petrovitsch <bernd@firmix.at>
To: Yaroslav Rastrigin <yarick@it-territory.ru>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
andersen@codepoet.org, linux-kernel@vger.kernel.org
Subject: Re: Why the DOS has many ntfs read and write driver,but the linux can't for a long time
Date: Mon, 09 Jan 2006 15:32:39 +0100 [thread overview]
Message-ID: <1136817159.5785.47.camel@tara.firmix.at> (raw)
In-Reply-To: <200601091403.46304.yarick@it-territory.ru>
On Mon, 2006-01-09 at 14:03 +0300, Yaroslav Rastrigin wrote:
> Hi,
> > > > money to the right people.
> > >
> > > Could or would you be so kind to provide at least moderately complete
> > > pricelist ? Whom and how much should I pay to have correct support for
> > > intel graphics chipset, 2200BG Wi-Fi, complete
> > > suspend-to-disk/suspend-to-ram and to get an overall performance boost ?
> >
> > Since these are all supported in 2.6.15, $0 would be my quote.
> I've mentioned _correct_ support. Contrary to current rather sad state of things.
> 855GM still has no support for non-VESA videomodes (1280x800 can be enabled only via VBIOS hacks, and is not always properly restored on resume)
> (and don't supported with intelfb) (which, AFAIK, has no support for dualhead)
> 2200BG sometimes starts to unacceptably lag and drop packets after going out of suspend (either STR or STD) and until reboot.
> (And this is driver issue)
> Suspend to ram works, more or less, but drains power like hungry cat drinks milk, and I just can't leave my laptop in STR for more than two days
> without worrying about my on-the-road availability.
> Suspend to disk has nasty tendency to ruin my whole hot live X session, since X can't properly restore VT on resume.
> Overall performance isn't that bad, either, but I just can't understand, why KATE (Kde more or less advanced editor) takes twice as long to start
> as UltraEdit in _emulated_ (VMWare) Windows XP running on this same box.
>
> So, the question remains the same - whom and how much I need to pay to solve abovementioned problems ?
The best place to ask this question is IMHO the respective development
lists and/or maintainers. If both of this does not exist, find recent
patch submitters (who provided patches for more than whitespace and
similar cleanups) and ask them.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2006-01-09 14:32 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 7:54 Why the DOS has many ntfs read and write driver,but the linux can't for a long time Boxer Gnome
2006-01-09 8:06 ` Erik Andersen
2006-01-09 8:21 ` Boxer Gnome
2006-01-09 8:53 ` Jim Crilly
2006-01-09 9:07 ` Yaroslav Rastrigin
2006-01-09 10:22 ` Alistair John Strachan
2006-01-09 11:03 ` Yaroslav Rastrigin
2006-01-09 12:45 ` CaT
2006-01-09 13:34 ` Yaroslav Rastrigin
2006-01-10 13:29 ` Helge Hafting
2006-01-10 16:29 ` Randy.Dunlap
2006-01-11 2:29 ` David Nicol
2006-01-11 2:56 ` Lee Revell
2006-01-12 18:53 ` David Nicol
2006-01-12 21:05 ` Lee Revell
2006-01-09 13:36 ` Kasper Sandberg
2006-01-09 13:56 ` Yaroslav Rastrigin
2006-01-09 16:07 ` Alan Cox
2006-01-09 16:15 ` Lee Revell
2006-01-09 16:34 ` Alan Cox
2006-01-09 16:34 ` Olivier Galibert
2006-01-09 19:24 ` Diego Calleja
2006-01-09 19:33 ` Lee Revell
2006-01-09 13:54 ` Lee Revell
2006-01-09 14:51 ` [OT?] " Yaroslav Rastrigin
2006-01-09 15:15 ` Lee Revell
2006-01-09 15:36 ` Randy.Dunlap
2006-01-14 9:55 ` Pavel Machek
2006-01-09 15:17 ` Pekka Enberg
2006-01-09 14:32 ` Bernd Petrovitsch [this message]
2006-01-09 15:22 ` Denis Vlasenko
2006-01-09 19:07 ` Diego Calleja
2006-01-09 22:49 ` Dave Airlie
2006-01-10 12:00 ` Pavel Machek
2006-01-09 13:56 ` Lee Revell
2006-01-10 7:13 ` Andrew Morton
2006-01-10 7:33 ` Denis Vlasenko
2006-01-10 8:33 ` D. Hazelton
2006-01-10 10:49 ` Diego Calleja
2006-01-10 13:26 ` Denis Vlasenko
2006-01-11 4:57 ` D. Hazelton
2006-01-10 9:32 ` Yaroslav Rastrigin
2006-01-10 9:20 ` Yaroslav Rastrigin
2006-01-10 10:50 ` Diego Calleja
2006-01-09 16:32 ` Bernd Petrovitsch
[not found] <5t06S-7nB-15@gated-at.bofh.it>
[not found] ` <5t34G-3Zu-21@gated-at.bofh.it>
[not found] ` <5t5pU-7tD-37@gated-at.bofh.it>
[not found] ` <5t5JU-7Sn-11@gated-at.bofh.it>
2006-01-09 14:18 ` Robert Hancock
2006-01-09 14:28 ` Oliver Neukum
2006-01-09 15:15 ` Lee Revell
2006-01-09 16:02 ` Oliver Neukum
2006-01-09 16:04 ` Lee Revell
2006-01-09 16:14 ` Oliver Neukum
2006-01-09 16:19 ` Lee Revell
2006-01-09 16:29 ` Bernd Petrovitsch
2006-01-09 16:41 ` Lee Revell
2006-01-09 16:53 ` Oliver Neukum
2006-01-09 16:56 ` Lee Revell
2006-01-09 17:14 ` Olivier Galibert
2006-01-09 17:28 ` Lee Revell
2006-01-09 19:35 ` Anton Altaparmakov
2006-01-09 17:14 ` Bernd Petrovitsch
2006-01-09 17:31 ` Alan Cox
2006-01-09 16:45 ` Jeff V. Merkey
2006-01-09 17:33 ` Lee Revell
2006-01-09 18:11 ` Marcin Dalecki
2006-01-09 17:45 ` Oliver Neukum
2006-01-09 16:59 ` Bernd Petrovitsch
2006-01-10 1:44 ` Alistair John Strachan
2006-01-10 4:30 ` Lee Revell
2006-01-10 10:13 ` Jakob Oestergaard
2006-01-10 10:34 ` Jesper Juhl
2006-01-10 23:48 Lukas Hejtmanek
2006-01-10 23:57 ` Lee Revell
2006-01-11 0:02 ` Lukas Hejtmanek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1136817159.5785.47.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
--cc=yarick@it-territory.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).