Searched refs:recognise (Results 1 – 10 of 10) sorted by relevance
484 u32 recognise = ETH_ARC_AB; /* always accept broadcasts */ in korina_multicast_list() local488 recognise |= ETH_ARC_PRO; in korina_multicast_list()492 recognise |= ETH_ARC_AM; in korina_multicast_list()505 recognise |= ETH_ARC_AFM; in korina_multicast_list()515 writel(recognise, &lp->eth_regs->etharc); in korina_multicast_list()
56 XFree86 likely can be configured to recognise the remote keys. Once I
114 otherwise. Kernel can recognise stacked interfaces because their
49 With 2.4 kernels, DECnet would only recognise addresses as local if they
148 - Sometimes the driver will not recognise the DAC, and the
11 bits) you have supplied. Binfmt_misc can also recognise a filename extension
281 recognise the blob format and will not return -EBADMSG to indicate it is
306 Note that CacheFiles will erase from the cache any file it doesn't recognise or
215 Now it is easy to see that on Intel it is quite easy to recognise a kernel598 3) The compiler was clever enough to recognise that it could return the1218 1) A kernel address should be easy to recognise since it is in1221 2) Another backchain should also be easy to recognise since it is an
176 The solution is relatively simple - it just took a long time to recognise it.