Jump to content
InsanelyMac Forum

DaemonES

Members
  • Content count

    294
  • Joined

  • Last visited

About DaemonES

  • Rank
    InsanelyMac Sage
  • Birthday 09/09/1985

Contact Methods

  • Website URL
    http://
  • ICQ
    337416164

Profile Information

  • Location
    Kiev, Ukraine
  1. DaemonES

    ESI Juli@ / Envy 24 with OSX86 - Any progress?

    IOFilterInterruptEventSource should submit 2 callbacks. One which return bool (does interrupt is yours or not) - filter, second callback - handler would be called if filter returns true. So you may print from interrupt handler routine, but not from filter. Anyway, use GDB to analyze crash dumps.
  2. DaemonES

    ESI Juli@ / Envy 24 with OSX86 - Any progress?

    Forget about serial. In audio driver you should work in primary interrupt context. If you will block for several milliseconds then you will gen an interrupt look up and crash of the system. You also should not use IOLog from interrupt routine, maybe firewire, but not sure. Also remember about with OS X and multiple DMA mode in Envy24HT. You should use separate DMA buffer for each two channels.
  3. DaemonES

    Realtek 8168/8111 solution

    lol No, use windows drivers instead.
  4. DaemonES

    Realtek 8168/8111 solution

    rtl2news do not touch you computer, it can damage you brain. Boot in singleuser mode and rm -R /System/Library/Extensions/RealtekR1000.kext
  5. /dev/mem is no longer exists in Mac OS X. You can turn it on: pass kmem=1 to boot-args, but /dev/mem in this case doesn't work properly.
  6. DaemonES

    Realtek 8168/8111 solution

    MisterJack {censored} no!!! Read first post. Do you see you RTL chip here? Do you see any WiFi note?
  7. DaemonES

    ESI Juli@ / Envy 24 with OSX86 - Any progress?

    Who cares about Hackintosh users? this is not market for a large company. They spent money to pay salary for several programmers for several moths. This is not cheap.
  8. DaemonES

    ESI Juli@ / Envy 24 with OSX86 - Any progress?

    They declare list of Operation Systems, that they will support. If you chose another OS, it's your problem. And this is not ESI responsibility. If you want to use Juli@ in Minix 3, does ESI have to write drivers for Minix? )))))))))))))))))))))))
  9. DaemonES

    Attansic L1 Driver Project

    Try to sudo rm -R /System/Library/Extensions/AttansicL1Ethernet.kext sudo touch /System/Library/Extensions sudo reboot It seems someone included unworkable version of driver to DVD. Stupid decission include unstable SW.
  10. DaemonES

    Attansic L1 Driver Project

    Тупые буржуи undefined look better! And do not post noob questions in the development thread.
  11. DaemonES

    Attansic L1 Driver Project

    Not really, look to the FreeBSD driver. Attansic L1 has several revisions, sometimes Linux driver doesn't work too. Autonegotiation works, but setting of 1 gigabit mode not. Anyway, good job. I was afraid, that nobody can finish my job
  12. DaemonES

    Attansic L1 Driver Project

    Direct port coudn't be done.
  13. DaemonES

    Attansic L1 Driver Project

    Mail me. I will forward to you a mail of those guy, who have done port for FreeBSD. He said, that anyway performance is poor.
  14. DaemonES

    Attansic L1 Driver Project

    FreeBSD now has Atheros driver too, and it looks good. So, somebody can use it to write new driver http://people.freebsd.org/~yongari/age/
  15. DaemonES

    Attansic L1 Driver Project

    Well Attansic L1 DMA completely not understandable for me. This stupid hacks with RRD descriptors and so on. The right way is complete port from other OS. But sometimes it doesn't work, like in this case. DMA part of Linux atl1 is completely the same as in vendor driver written bu Attansic. Code is very poor. Maybe someday they will release specification, but until that... I know, that one guy start merging atl1 and atl2 in atlx driver, that will have one codebase. Maybe in this case code will be more clear for me.
×