use opengl instead of xv. Nicer picture, better colours and the cpu load is neglible. So what is the problem?
Announcement
Collapse
No announcement yet.
AMD Catalyst 9.8 Delivers New Kernel Support
Collapse
X
-
Originally posted by cheung View PostI know that, but there is really no other better option?
I can compile lastest open source radeon and drm driver, but it does not have 3D support.
I can't use radeon with 3D visual effect of compiz or Kwin.
Comment
-
Originally posted by Tares View PostOkay, but don't get your hopes too high :/ although tropics improved quite a lot, but that because I've got errors in rendering :/ whole benchmark was missing water and screen was flickering before I've turned aa on so something is wrong with this drivers.
Comment
-
Originally posted by energyman View Post??? wtf?
emmm... bkl is in linux since it can do smp. So at least 2.0. <Preemptive kernel? of course! for ages.
and as for general preemption i recall fglrx DID NOT like it and DID spew shitty messages into dmesg (and maybe even worse things).
and by the way was the module_license problem resolved?
Comment
-
Symbol: PREEMPT_VOLUNTARY [=y] │
│ Prompt: Voluntary Kernel Preemption (Desktop) │
│ Defined at kernel/Kconfig.preempt:19 │
│ Depends on: <choice> │
│ Location: │
│ -> Processor type and features │
│ -> Preemption Model (<choice> [=y])
and preempt:rcu:
│ This option reduces the latency of the kernel by making certain │
│ RCU sections preemptible. Normally RCU code is non-preemptible, if │
│ this option is selected then read-only RCU sections become │
│ preemptible. This helps latency, but may expose bugs due to │
│ now-naive assumptions about each RCU read-side critical section │
│ remaining on a given CPU through its execution. │
│
so I stay with no. Because rcu bugs can result in data corrpution. I like the stuff on my harddisks.
Comment
-
Originally posted by energyman View PostSymbol: PREEMPT_VOLUNTARY [=y] │
│ Prompt: Voluntary Kernel Preemption (Desktop) │
│ Defined at kernel/Kconfig.preempt:19 │
│ Depends on: <choice> │
│ Location: │
│ -> Processor type and features │
│ -> Preemption Model (<choice> [=y])
and preempt:rcu:
│ This option reduces the latency of the kernel by making certain │
│ RCU sections preemptible. Normally RCU code is non-preemptible, if │
│ this option is selected then read-only RCU sections become │
│ preemptible. This helps latency, but may expose bugs due to │
│ now-naive assumptions about each RCU read-side critical section │
│ remaining on a given CPU through its execution. │
│
so I stay with no. Because rcu bugs can result in data corrpution. I like the stuff on my harddisks.
Comment
Comment