thanks, btw if we change date and time of our offline laptop before we generate address would that make our address more secure ?

There are mulitple types of security here.

First, do you trust the source where you downloaded the software.... ?
I build from the source-code itself to be sure my executable doesn't do anything unexplained.

The second type of security has to do with the ECSDA key generation.
This is linked to your SSL library.
Since it uses entropy to make key generation unique, it would even be hard for your computer to regenerate the same result.
Modern entropy uses time, (cpu) temperature readings, harddisk head locations etc etc to make it unique.

Then there is the security of you home network.

Etc etc.

As you can see if you play with the program is that for each extra character you add the time to get the address is multiplied by 60.
Even if you generate an address with the first 9 char in a preferred state, in order to get access to this address anyone else will have
to generate all 35 chars.

thats actually bad!
if you want to seed a brainwallet. get some "random" input (aka entropy) and seed the brainwallet with that.

Use notepad++ and a few params to delete anything that doesn't start with the right word or something else.

http://superuser.com/questions/290247/how-to-delete-all-line-except-lines-containing-a-word-i-need

Someone could make it work in the pimp distribution? (based on debian)

That would only be needed if you don't generate the address yourself.
You will need the private key to get access to your wallet.

The software has switches for this. A master public key that only you have the private key for can be used in
the generation process. The result private key (wif format) and your private key (also wif) can be combined
using the keyconv utility. This private key is now only known to you.

There is even a pool for this @ vanitypool(dot)appspot(dot)com

yep that is what this pool does.
this is a three stage operation.
1- your create a key palr (priv key, publc key) that also yields a non vanity bitcoin address, for example on electrum, preferably more secure on your own system.
2- upload the request for a vanity address and the public key to this pool or another service that has the processing power.
3- retreive the priv key from this pool. The actual address generation routine only uses public keys.

combine this priv key(unsecure) with your priv key(secure) to generate a new priv key(secure).
(an online utitlity to do this is here gobittest(dot)appspot(dot)com/VanityAll
but since it is on the internet it is less secure than running the keyconv util)
this new priv key gives you the vanity address.

I haven't had any issues getting it to work with the GPUs I've got - but it wouldn't be too surprising if the OpenCL code needs adjustments for some hardware (as it has in the past for AMD cards).

But as far as ASICs go - not going to work.  ASIC mining equipment performs a very specific task, and that task is not part of address generation.  You'd have to develop an ASIC for vanity mining, which is not cost-effective at all.  You *might* be able to get somewhere with FPGAs, but I suspect it's still not cost-effective compared to an off-the-shelf GPU.

I've never had to jump through hoops to get things working - lucky that way, I suppose; I know there's plenty of people with issues getting it working, having to mess with drivers, etc.
As you now mention 280x (as opposed to x280 - I wish they wouldn't both use similar model numbers ), check out the lifeboat version and start reading at this post:
https://bt.irlbtc.com/view/301068.msg3898427#msg3898427

Might also read around in that thread (and this one) in general.  Pretty sure there's other musings about getting things running on the 280x