• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Regarding dual headed IOFramebuffer instances
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Regarding dual headed IOFramebuffer instances


  • Subject: Regarding dual headed IOFramebuffer instances
  • From: selvaganesan <email@hidden>
  • Date: Tue, 27 Feb 2007 12:05:52 +0530

Dear all,

IOFramebuffer subclasses may implement functionality where a single
framebuffer drives multiple displays. This is not recommended or fully
supported and instead multihead cards should implement multiple
instances of IOFramebuffer objects to provide full functionality.

1. Why can't we implement full functionality of extended display with
single head cards?
2. Has multihead a two IOFrameBuffer objects to support extended display?

Thanx in advance

selva.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: RE: Passing arguments to application lauch through KUNCExecute() call
  • Next by Date: Re: Passing arguments to application lauch through KUNCExecute() call
  • Previous by thread: Re: Sandboxing KEXT
  • Next by thread: Debugging a Kernel Panic
  • Index(es):
    • Date
    • Thread