As I exclusively shared earlier today, an AMD source I reached out to has said that "Catalyst won't support Wayland anytime soon." Meanwhile NVIDIA has filed Wayland support as a "feature enhancement request" that they will be evaluating the effort and benefits of supporting Wayland in addition to X.Org.
Binary driver support for Wayland likely won't come from either AMD or NVIDIA in the near-term, but looks like if anything it will first come out of the NVIDIA camp -- to not much surprise. Even after delivering Wayland support though they'll be likely to drop X11 support in the foreseeable future due to legacy and enterprise support needs. On the NVIDIA side their shared Unix graphics driver code also needs to support FreeBSD and Solaris, where there is no Wayland support planned by upstream and only the X.Org Server.
AMD not aggressively supporting Wayland isn't entirely surprising since new Linux-specific features to the Catalyst driver tend to come rather slow, even when it comes to supporting new Linux kernel and X.Org Server releases that generally require small modifications to support the new API/ABI. Generally this support doesn't come until the change is necessitated by Ubuntu or one of AMD's supported enterprise Linux distributions (i.e. Red Hat Enterprise Linux and SUSE Linux Enterprise). Wayland 1.0 also isn't even being released until later this calendar year -- where there will be API and protocol stability -- with the current version being Wayland 0.95.
For now if you want to toy around with Wayland/Weston, you basically need to use one of the main open-source drivers: Intel, Radeon, or Nouveau. Running Wayland works but a lot remains as shown from testing a recent Wayland LiveCD. Ubuntu has also delayed their Wayland system compositor into next year.
Wayland will be talked about next week at the GStreamer 2012 Conference in San Diego alongside LinuxCon North America 2012. Wayland is also a topic for next month's XDC2012 in Nürnberg where maininling XWayland will also be debated.